-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Segmentation Fault trying to edit file in Mac Sonoma #8415
Comments
Segfaults are usually caused by buggy tree-sitter scanners (which are written in C/C++). Can you narrow down which file is causing this? |
here are the steps:
this seems to be happening with |
@the-mikedavis looks like the issue might be something with rendering git gutter |
I tried following steps:
|
yeanh that is a known issue that is fixed on master for a long time (#7227). Its caused by compiling with a newer rust compiler. The issue is not present in the official release binary or master. This is an issue with the homebrew package |
Thanks. I used the one from GitHub Releases and it works great |
This issue shares a common characteristic with other issues. It's another example why the infrequent release schedule isn't a good idea. Users on the official release run into bugs months after they have been fixed because the project doesn't release (here: last released in May, fixed June, bug as of October). Unfortunately, the maintainers seem unwilling to fix their release process to release more frequently. #6362 |
Summary
I did clean install of Mac osx sonoma on my silicon Mac. after installing helix using home-brew, I noticed that I am getting segmentation fault while trying to edit files in some projects.
just open some file in the project and press
o
to open line. it gives segmentation fault.it is not happening in all projects. but it few projects it happens always consistently.
Reproduction Steps
No response
Helix log
~/.cache/helix/helix.log
Platform
macOS
Terminal Emulator
wezterm 20230712-072601-f4abf8fd
Helix Version
helix 23.05 (7f5940b)
The text was updated successfully, but these errors were encountered: