-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when joining channel on macOS Catalina/BigSur #5384
Comments
I know this crash could be anything but this issue mentions an interesting bug in xcode 15: transmission/transmission#6353 I couldn't find much else, I tried to use an much older build but as makes sense it's not possible to collaborate using too old of a build. |
#4633 seems like it might be the same crash |
@gabydd The good news is that I can reproduce this on Catalina! (The less good news, is I don't know how to fix it – yet!). |
@gabydd I looked through the old correspondence history with my colleagues, where we were testing collaboration in Zed, and it turns out that on 01.12.2022, it was still working successfully on macOS Big Sur. Somewhere during the next six months, this crash appeared.. |
A lot has changed :D. I know that they recently released a new LiveKit that may fix a different crash we were seeing, so I'll give that a go; but it's also possible that we've changed how we use it. |
Attaching my environment / crash log here for reference: EnvironmentZed: v0.149.5 (Zed) macOS crash report:Process: zed [20453] Path: /Applications/Zed.app/Contents/MacOS/zed Identifier: zed Version: 0.149.5 (20240822.190532) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: zed [20453] User ID: 501 |
Check for existing issues
Describe the bug / provide steps to reproduce it
Discord user
gabydd
reported running into:They also experienced this issue on Big Sur
Environment
Zed: v0.119.16 (Zed Preview)
OS: macOS 10.15.7
Memory: 4 GiB
Architecture: x86_64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.If you only need the most recent lines, you can run the
zed: open log
command palette action to see the last 1000.crash.log
The text was updated successfully, but these errors were encountered: