-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Kitty on gentoo segfaulting with nvidia opengl #5662
Comments
A bit more information. The kernel log shows kitty[30393]: segfault at 0 ip 0000000000000000 sp 00007fff4f3792e8 error 14 That apperas to be error 14 : attempt to execute code from an unmapped area. If I could figure out what library it was in when this happens, I could probably get to the bottom of things, but as I mentioned before, any kinds of debugging seems to cause things to work without error. |
Simply rollback your nvidia gpu drivers to find the problem version. And you dont need to run with strace or gdb to get a stack trace you can make debug Although I am 99% certain this crash will not be in kitty code but in Unfortunately I dont own any nvidia hardware so I cant help you with it. |
My distro does not currently have the older version available since they had security issues. Also, from working to not working, no nvidia upgrade was done, so it is some other interaction. I've been going through a list of the software that was updated and I have yet to find one that I can downgrade to fix the issue. I don't have coredumpctl on my system, but you are right, I should be able to tell the system to dump a core and debug from there. Thanks. I agree it is most likely not in kitty code directly, but I having trouble getting a suspect to go after. |
Argh! It is in /usr/lib64/libnvidia-tls.so.390.154, but that is both working and not working depending on other updates. The thing right before it on the stack is kitty/fast_data_types.so. Any idea on what it would be trying to do? That could help me identify the culprit. |
Build kitty from source with make debug and the stack trace will tell |
Thanks for helping. The debug shows it running ret = pthread_create(&self->io_thread, NULL, io_loop, self); I don't think I'm understanding what I'm seeing. Does the following suggest any suspects to you? #0 0x0000000000000000 in ?? () |
libnvidia-tls almost certainly does some management of thread local |
Thanks again for your help, you've given me a few more things to look into. However, it looks like I'm probably going to have to wait for an nvidia update. At least my work machine uses something else. Just another reason to continue replacing the nvidia cards I've been using. I miss the day when they were a sure bet. |
That's unlikely -- and even if there's one last release it probably won't address much, NVIDIA is dropping support 390.x branch that you're using next month. It's also the only branch with the libnvidia-tls double version nonsense (Edit: one breaks xorg drivers, the other breaks other things). In Gentoo the 390 drivers will be masked w/ a security notice sometime next year (I can say that because I'm the maintainer for it), albeit still kept for as long as they kinda work (but really wouldn't expect much support for 390, your only real options is either new hardware or using nouveau). |
Thanks. That's good to know. I guess it's time for that ATI card I've been looking at. |
I've been experiencing a similar fate with the most recent kitty build in Portage(Gentoo), I use the same 390.x nvidia drivers, and can confirm that when using gdb a segmentation fault does not happen. My backtrace looked similar to what has been shown in this thread, but, suprisingly, I was able to just build kitty from source(not in debug mode), and now the built binary runs fine without any segmentation faults. |
Describe the bug
After some recent updates to my system, kitty started segfaulting. Lots of frustrating debugging later, I've narrowed things down to issues with nvidia cards on the systems seeing the issue. Similar systems with an ATI card do not display the same problem. The segfault occurs shortly after creating the window, ie you will see a window flash up and then go away.
To futher complicate the debugging, trying to run kitty under strace or gdb results in kitty working fine, so I can't use those to figure out what is causing the segfault.
I don't know which package updates set things off, but I have one system where I have rolled back to the weekend's snapshots to get things working again and another system that I've left broken to try to debug things and get to the bottom of it.
To Reproduce
Steps to reproduce the behavior:
Screenshots
NA
Environment details
gentoo
kitty 0.26.4 and 0.26.5 have both been tried
mesa 22.1.7 and 22.2.3 have both been tried
what else can I provide to help to get to the bottom of this?
Additional context
Same result with kitty --config NONE
The text was updated successfully, but these errors were encountered: