-
Notifications
You must be signed in to change notification settings - Fork 1.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
Sway sometimes segfaults when closing VSCode window #7506
Comments
Very odd stacktrace, why is it removing the keyboard? Seems to be more of a wlroots crash (happens here 1). Can you share the sway debug logs? |
Not today, but I will try to get it tomorrow. |
When trying to brute force the crash, I was unable to reproduce this exact stacktrace. But several different crashes happened instead. The one that happened most often is this:
But it happened when starting VSCode, not when stopping it (after several starts and stops it eventually crashes). |
Also I got this:
|
This time I got this crash:
The last rows of the debug log:
|
The piece of code in wlroots from that stacktrace has not change in a while, could this be a client error taking the compositor down? Would you be able to get any kind of log/stacktrace from VSCode? |
And I'm getting this kind of crash for a while (since sway 1.8 update).
I know that when sway crashes with an abort (like in #7506 (comment)), VSCode also dumps core. But I did not look into it. I install VSCode form flatpak and I'm not sure if I can install debug symbols for apps in flatpak. When sway segfaults, VSCode does not dump core.
|
For some reason launching VSCode with |
This crash happened not when closing VSCode, but when I was working with Steam app:
Last lines of the debug log:
|
New crash:
|
Also this one when switching workspaces:
|
Here is one more:
|
Similar segfaults with microsoft-edge-stable-bin on Wayland. See https://bbs.archlinux.org/viewtopic.php?id=285213 |
Sway Version:
Debug Log:
I didn't get a debug log for this. If you need it, I can try to get it.
Configuration File:
I didn't try to reproduce with default configuration, but I can try it if needed.
Stack Trace:
I started seeing this since the 1.8 update. I thought it's #7303, but then 1.8.1 came out with a fix of that issue, and crashes sometimes happened even after this. I was trying to get a stacktrace for some time, but for some reason I was unable to install the debug symbols correctly on my system, so gdb stacktraces did not contain any useful information.
Now I was finally able to get a meaningful stacktrace so I'm reporting this as @bl4ckb0ne asked me.
The text was updated successfully, but these errors were encountered: