Cwtch Crashes on x64 Macs when creating/loading profiles. #542
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#542
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Thanks Sarah. When I get a chance in the next few days I'm going to run the combo update on that machine. I am getting some buggy stuff happening on it and it won't hurt to eliminate that as a factor in this issue. Unless some other early darwin folks weigh in with confirmation in the mean time.
Per CRCT: "it's running fine on 10.15.7 (Catalina) but not on 10.13.6 (High Sierra)"
Given the changes made between those two versions (including the splitting of system and data drives), it is looking more likely that this is an SDK issue.
High Sierra (10.13.X) is officially unsupported by Apple as of November, 2020 - which further points to this being an SDK difference - and likely one that we cannot resolve without unrealistic effort.
(That being said, maybe there is a nice
--please-support-older-macs
flag buried in xcode. Probably worth a small check)That being said, we should sit down and come up with a support plan for Mac (and likely other operating systems) that outlines what versions we can support, and how we deal with OS updates.
We currently target Cwtch builds to macOS 11.0 (officially supported, but not the most recent). Currently macOS 12 is nearly a year old, and macOS 13 is in public beta. We should draw up a support chart and make sure we are planning infrastructure upgrades to match (and surface supported OS's on the website / handbook)
I had a feeling it might be a SDK issue :/ I'll hazard a guess that lots of devs are dealing with backporting issues like this one. Sigh...
Fingers crossed that there's something helpful in xcode but I'm not going to hold my breath.
I agree that a support chart as you suggest would be a good plan.
Otherwise, see my relpy on CRCT
and thanks!
Closing this under the assumption that this crash is happening on a version of Mac that is explicitly out of support: https://docs.cwtch.im/docs/getting-started/supported_platforms