Sway crashed with SIGABRT #6490
Labels
bug
Not working as intended
Comments
|
Would be helpful to have a trace with wlroots debug symbols. |
This comment has been minimized.
This comment has been minimized.
|
This is unrelated, tracked separately in swaywm/wlroots#3173. |
|
@emersion Ah, ok, thanks for the heads-up. |
Does this imply building without |
|
Yeah, building without Alternatively, could just use a manually compiled Sway for a while. |
|
I believe this should have more information: I'm currently reproducing this by running these two simultaneously: They're both Electron apps running via Wayland. It doesn't always crash, but chaging the split from vertical to horizontal or moving the windows a bit helps [to trigger the crash sway]. I'll go ahead and try |
|
None of the applications that cause the crash run with sway [and wlroots] master. Even chromium itself no longer runs: |
|
Ah, yes, this is swaywm/wlroots#3168. |
|
I'm not sure I fully completely I understood correctly: chromium crashing on sway-master is the linked issue. But sway 1.6.1 itself crashing as reported here is a separate issue, right? |
|
Yes. But many changes made it into master since 1.6.1. So a reproduction with something else than master isn't too useful. |
|
I've reproduced this on |
|
Hm, this is triggered on |
|
Do you have a debug log of this? |
|
Reproduced with sway's log it too big to post here, and neither paste.sr.ht or gist.github.com let me paste something that big. Github also won't let me attach the file itself here, so I put it all into a ZIP. |
|
Hm, the abort cause isn't printed in that log, unfortunately. I guess the next stop would be to try to compile Mesa with debugging symbols and see where the abort is happening in Mesa. Maybe looking at dmesg could give some clues as well, but not sure i915 will log anything. |
|
Dump with mesa with debug symbols:
|
|
I'm using sway-master, and wlroots-master with swaywm/wlroots@d290b13 reverted. |
#ifdef DEBUG
const bool color = INTEL_DEBUG & DEBUG_COLOR;
fprintf(stderr, "%siris: Failed to submit batchbuffer: %-80s%s\n",
color ? "\e[1;41m" : "", strerror(-ret), color ? "\e[0m" : "");
#endif
abort();This is definitely a Mesa bug. Please report it to them. |
|
Thanks. Reported as https://gitlab.freedesktop.org/mesa/mesa/-/issues/5366 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please fill out the following:
Sway Version:
Debug Log:
Sorry, I can't repro this. I was switching workspaces to one with an electron app. I doubt that's useful, but I find that sway only crashes when Electron is around.
If I get another similar crash, I'll follow up here with more details.
https://git.sr.ht/~whynothugo/dotfiles/tree/29b1528db1dce22f65398bd6dd25e83eee199036/item/home/.config/sway/config
coredumpctl gdb swayand thenbt fullto obtain the stack trace.The text was updated successfully, but these errors were encountered: