Regular Crash #261

hadarvc · 2026-04-26T20:15:53Z

hadarvc
Apr 26, 2026

I am crashing regularly (1 to 2 times a day) for the past week+. It might not be a scroll bug, but it's certainly causing scroll to crash, reliably. Anecdotally, it seems to have started around the time that Wayland 1.25 was released. I have no idea if that's related. I've also been through at least 2 linux kernel upgrades since it started, and it continues to crash.

The circumstance is a little weird, which is why I'm really hesitant to point the finger at scroll.

I run Chrome Stable and it automatically comes up in WS5.

A few weeks ago I started regularly running a Python script with Playwright. It launches another copy of Chrome (completely separate blank profile in /tmp) and automatically moves it to WS11. This worked for weeks without a single crash. I could work for 10 hours in a day, bouncing around between WS5 and WS11 (and everything else I do during the day) with no issues.

Then, a little over a week ago, with a number of scroll updates as well, at least once a day, occasionally twice, when I hit Mod3+5 to go to the "real" Chrome, scroll crashes. It doesn't matter where I am, meaning I can be in a terminal window in WS1 and hit Mod3+5 and it will crash, it doesn't have to be coming from WS11, though that happens with regularity as well.

I haven't turned on any debugging in scroll yet (he says sheepishly), partially because I can immediately type scroll again, instantiate windows (that all offer "Restore Pages"), etc., so I'm back in business pretty quickly. But, I'm getting tired of it...

Anyway, with no debugging on, and I can't copy/paste the errors on screen (because I'm in a login shell session after the crash), I took an actual photo of one of the crashes, in case anyone has an AHA, that's obvious...

If this looks like something that will only be solved by running in full debug mode, let me know. I can look up my old notes from when I last ran it that way, or you can point me to any current best practices for doing that.

Thanks for taking a look!

P.S. I just looked at the image again and this particular crash came from a Brave instance. Meaning, I pressed Mod3+5 when on WS3 which had Brave opened to Perplexity.ai. I didn't want anyone to think that it was a Chrome to Chrome error, or anything to do with Playwright, etc.

Answered by hadarvc

May 21, 2026

I'm guessing that you can close this. I have run without a hitch on the git version (no debug) for almost a week, with multiple updates of scroll and a few kernel updates as well, and it's been rock solid, with me banging on it exactly the same way that was making it crash reliably before. I'll own a new discussion or issue if/when it occurs again, with the dumpctrl output.

View full answer

dawsers · 2026-04-26T20:55:18Z

dawsers
Apr 26, 2026
Maintainer

scroll should never crash unless there is a graphics driver or other low level bug, which doesn't seem to be the case. I don't like to have crashing bugs, so I appreciate you raising this issue, and any help you can provide debugging it.

With your description, it will be a bit hard for me to replicate the problem. I would also need to have a look at the script you are using to launch Playwright and the Chrome worker, etc. So, if you can make it crash reliably, it is much better you run a debug version of scroll and post a stack trace when it crashes, so we can start from there.

git clone https://github.com/dawsers/scroll.git
cd scroll
meson setup --buildtype debug build-debug
ninja -C build-debug/
# Launch scroll and make it crash
./build-debug/sway/scroll --debug

Edit: And then, of course, post the stack trace

coredumpctl dump scroll

or if you have gdb

coredumpctl gdb scroll
(gdb) bt full

19 replies

dawsers May 12, 2026
Maintainer

I don't need the whole thing, because it is a release build, so I wouldn't be able to do much with the debugger. What I would like to get is the first page or so, where I can see the stack trace of the thread that crashed.

There is usually a header with the PID, UID etc, and then a few stack traces. The first block is the one that crashed, something like:

Stack trace of thread 208559:
                #0  0x000056156d435de9 apply_container_sizes (/home/work/dawsers/master/build-release/sway/scroll + 0xb8de9)
                #1  0x000056156d43c7bf layout_toggle_size_change_focus (/home/work/dawsers/master/build-release/sway/scroll + 0xbf7bf)
                #2  0x000056156d3ea2b5 seat_set_focus (/home/work/dawsers/master/build-release/sway/scroll + 0x6d2b5)
                #3  0x000056156d42b95a workspace_switch (/home/work/dawsers/master/build-release/sway/scroll + 0xae95a)
                #4  0x000056156d411b5c cmd_workspace (/home/work/dawsers/master/build-release/sway/scroll + 0x94b5c)
                #5  0x000056156d3ba710 execute_command (/home/work/dawsers/master/build-release/sway/scroll + 0x3d710)
                #6  0x000056156d3fbc2a seat_execute_command (/home/work/dawsers/master/build-release/sway/scroll + 0x7ec2a)
                #7  0x000056156d3e58fd handle_key_event (/home/work/dawsers/master/build-release/sway/scroll + 0x688fd)
                #8  0x00007f67f8128590 wl_signal_emit_mutable (libwayland-server.so.0 + 0x8590)
                #9  0x000056156d4b62f0 wlr_keyboard_notify_key (/home/work/dawsers/master/build-release/sway/scroll + 0x1392f0)
                #10 0x00007f67f8128590 wl_signal_emit_mutable (libwayland-server.so.0 + 0x8590)
                #11 0x000056156d4b62f0 wlr_keyboard_notify_key (/home/work/dawsers/master/build-release/sway/scroll + 0x1392f0)
                #12 0x000056156d46d80c handle_keyboard_key (/home/work/dawsers/master/build-release/sway/scroll + 0xf080c)
                #13 0x000056156d46c85b handle_libinput_readable (/home/work/dawsers/master/build-release/sway/scroll + 0xef85b)
                #14 0x00007f67f812a3d2 wl_event_loop_dispatch (libwayland-server.so.0 + 0xa3d2)
                #15 0x00007f67f812c567 wl_display_run (libwayland-server.so.0 + 0xc567)
                #16 0x000056156d3b959a main (/home/work/dawsers/master/build-release/sway/scroll + 0x3c59a)
                #17 0x00007f67f7c27741 n/a (libc.so.6 + 0x27741)
                #18 0x00007f67f7c27879 __libc_start_main (libc.so.6 + 0x27879)
                #19 0x000056156d3b9785 _start (/home/work/dawsers/master/build-release/sway/scroll + 0x3c785)

hadarvc May 12, 2026
Author

OK, probably more than you need, but this is the full output on the console with the full dump redirected to the 262M file:

       PID: 63260 (scroll)
       UID: 1000 (hadar)
       GID: 1000 (hadar)
    Signal: 11 (SEGV)
 Timestamp: Fri 2026-05-01 22:07:58 EDT (1 week 3 days ago)

Command Line: scroll
Executable: /usr/bin/scroll
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (hadar)
Boot ID: d48bd060a658482a8ec6fd79678ec26a
Machine ID: c8bfae60f72b4ae1ab77f8c374647832
Hostname: hadarmini
Storage: /var/lib/systemd/coredump/core.scroll.1000.d48bd060a658482a8ec6fd79678ec26a.63260.1777687678000000.zst (present)
Size on Disk: 5.8M
Message: Process 63260 (scroll) of user 1000 dumped core.

            Stack trace of thread 63260:
            #0  0x0000558b03ca864d n/a (/usr/bin/scroll + 0xa464d)
            #1  0x0000558b03ca93af n/a (/usr/bin/scroll + 0xa53af)
            #2  0x0000558b03c5a262 n/a (/usr/bin/scroll + 0x56262)
            #3  0x0000558b03c9da8e n/a (/usr/bin/scroll + 0x99a8e)
            #4  0x0000558b03c8ca5f n/a (/usr/bin/scroll + 0x88a5f)
            #5  0x0000558b03c2bc50 n/a (/usr/bin/scroll + 0x27c50)
            #6  0x0000558b03c689ec n/a (/usr/bin/scroll + 0x649ec)
            #7  0x0000558b03c4c81b n/a (/usr/bin/scroll + 0x4881b)
            #8  0x00007f8c3c026590 wl_signal_emit_mutable (libwayland-server.so.0 + 0x8590)
            #9  0x0000558b03d13cd6 n/a (/usr/bin/scroll + 0x10fcd6)
            #10 0x00007f8c3c026590 wl_signal_emit_mutable (libwayland-server.so.0 + 0x8590)
            #11 0x0000558b03d13cd6 n/a (/usr/bin/scroll + 0x10fcd6)
            #12 0x0000558b03cd0839 n/a (/usr/bin/scroll + 0xcc839)
            #13 0x00007f8c3c0283d2 wl_event_loop_dispatch (libwayland-server.so.0 + 0xa3d2)
            #14 0x00007f8c3c02a567 wl_display_run (libwayland-server.so.0 + 0xc567)
            #15 0x0000558b03c21f73 n/a (/usr/bin/scroll + 0x1df73)
            #16 0x00007f8c3ba276c1 n/a (libc.so.6 + 0x276c1)
            #17 0x00007f8c3ba277f9 __libc_start_main (libc.so.6 + 0x277f9)
            #18 0x0000558b03c226b5 n/a (/usr/bin/scroll + 0x1e6b5)

            Stack trace of thread 63270:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63272:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63285:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63283:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63286:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63290:
            #0  0x00007f8c3bb1806d syscall (libc.so.6 + 0x11806d)
            #1  0x00007f8c3c21edee g_cond_wait (libglib-2.0.so.0 + 0x8cdee)
            #2  0x00007f8c3c1b822d n/a (libglib-2.0.so.0 + 0x2622d)
            #3  0x00007f8c3c1b829d g_async_queue_pop (libglib-2.0.so.0 + 0x2629d)
            #4  0x00007f8c3b28a51c n/a (libpangoft2-1.0.so.0 + 0xc51c)
            #5  0x00007f8c3c2284fc n/a (libglib-2.0.so.0 + 0x964fc)
            #6  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #7  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63287:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63288:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63289:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63264:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63280:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63284:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63266:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63271:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63267:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63268:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63282:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63279:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)

            Stack trace of thread 63281:
            #0  0x00007f8c3ba9ef32 n/a (libc.so.6 + 0x9ef32)
            #1  0x00007f8c3ba9339c n/a (libc.so.6 + 0x9339c)
            #2  0x00007f8c3ba9368c n/a (libc.so.6 + 0x9368c)
            #3  0x00007f8c3ba95e5e pthread_cond_wait (libc.so.6 + 0x95e5e)
            #4  0x00007f8c381ecb1e n/a (libgallium-26.0.6-arch1.1.so + 0x5ecb1e)
            #5  0x00007f8c381a1ebd n/a (libgallium-26.0.6-arch1.1.so + 0x5a1ebd)
            #6  0x00007f8c381eca5d n/a (libgallium-26.0.6-arch1.1.so + 0x5eca5d)
            #7  0x00007f8c3ba9697a n/a (libc.so.6 + 0x9697a)
            #8  0x00007f8c3bb1a2bc n/a (libc.so.6 + 0x11a2bc)
            ELF object binary architecture: AMD x86-64

dawsers May 12, 2026
Maintainer

Thank you. That is exactly what I needed. The problem now is we don't know what version of scroll the stack trace corresponds to. I tried compiling several versions from around May 1st, which is the date of the crash, but I haven't been able to find anything useful (the addresses don't correspond to those builds).

So I am going to need to ask you to install the latest git version, write down which version hash you are running, make it crash, and produce the same information you wrote above (stack trace from coredumpctl). Maybe that will get us closer to the problem.

I am sorry this is becoming a lot of work for you. Thank you.

hadarvc May 21, 2026
Author

I'm guessing that you can close this. I have run without a hitch on the git version (no debug) for almost a week, with multiple updates of scroll and a few kernel updates as well, and it's been rock solid, with me banging on it exactly the same way that was making it crash reliably before. I'll own a new discussion or issue if/when it occurs again, with the dumpctrl output.

Answer selected by dawsers

dawsers May 21, 2026
Maintainer

That's good news!

If the crash comes back, please open a new issue so we keep it clean.

Thank you!

Edit: Going through the list of changes around the time you mention, it seems this could be what fixed it for you.

hadarvc · 2026-04-26T22:01:29Z

hadarvc
Apr 26, 2026
Author

I'll build and run the debug version tomorrow. Thanks! Apr 26, 2026 4:55:51 PM dawsers ***@***.***>:

…

/scroll/ should never crash unless there is a graphics driver or other low level bug, which doesn't seem to be the case. I don't like to have crashing bugs, so I appreciate you raising this issue, and any help you can provide debugging it. With your description, it will be a bit hard for me to replicate the problem. I would also need to have a look at the script you are using to launch Playwright and the Chrome worker, etc. So, if you can make it crash reliably, it is much better you run a debug version of scroll and post a stack trace when it crashes, so we can start from there. git clone https://github.com/dawsers/scroll.git cd scroll meson setup --buildtype debug build-debug ninja -C build-debug/ # Launch scroll and make it crash ./build-debug/sway/scroll --debug — Reply to this email directly, view it on GitHub[#261 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/BGF44FMVZLAGFCNOPPKKCND4XZZUVAVCNFSM6AAAAACYHCSTL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNZSGE3DAMQ]. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS[https://github.com/notifications/mobile/ios/BGF44FJVE2DNG3JRPKA3OH34XZZUVA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGIYTMMBSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM] and Android[https://github.com/notifications/mobile/android/BGF44FMB4BW3N7G2KEONA5T4XZZUVA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRXGIYTMMBSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE]. Download it today! You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/BGF44FLW3IZBDB3EHBGYORL4XZZUVBFCNFSM6AAAAACYHCSTL6WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA74TMFJTSMVQXG33OUZQXK5DIN5ZA.gif]

0 replies

hadarvc · 2026-04-29T09:31:44Z

hadarvc
Apr 29, 2026
Author

Ok, I'll give that a try, thanks! Apr 29, 2026 4:21:17 AM dawsers ***@***.***>:

…

If you aren't getting any crashes, it could also be your build was referring to some library that was updated (you mentioned wayland 1.25 too), and having built the debug version, you fixed that by linking against the new version. If you use the AUR, it doesn't automatically flag packages out of date when one of their dependencies has been updated, so there are cases where the package may be in an unstable state and cause crashes. You can always rebuild/reinstall the package if you suspect that may be the case: paru -S sway-scroll # or, if you use the git version paru -S sway-scroll-git — Reply to this email directly, view it on GitHub[#261 (reply in thread)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/BGF44FPQAJT2IGEJFFQMCIL4YG3PFAVCNFSM6AAAAACYHCSTL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNZVGMYDQNA]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/BGF44FL3Y4OCQESYND2NRT34YG3PFBFCNFSM6AAAAACYHCSTL6WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQA76Q3ZJTSMVQXG33OUZQXK5DIN5ZA.gif]

0 replies

hadarvc · 2026-05-09T21:52:14Z

hadarvc
May 9, 2026
Author

Ok, seems worth a shot. Thanks. May 9, 2026 4:58:34 PM dawsers ***@***.***>:

…

OK. If you want, you can build a more "sensitive" debug version that should crash easily if there is any memory problem. I don't recommend running it in production, because it makes the system a bit slower. But if you want to test it to see if you finally get the crash, just replace the meson step above for the following one: meson setup --buildtype debug build-debug -Db_sanitize=address Like I said, if it doesn't produce the crash the first day you run it, you shouldn't run it again. It has quite a bit of overhead. — Reply to this email directly, view it on GitHub[#261 (reply in thread)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/BGF44FLRU3PQVU3JYXL2VXT4Z6LWZAVCNFSM6AAAAACYHCSTL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBWGUYDENI]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/BGF44FNQPMEVYAHC4VI5DDT4Z6LWZBFCNFSM6AAAAACYHCSTL6WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBAFLQDJTSMVQXG33OUZQXK5DIN5ZA.gif]

0 replies

hadarvc · 2026-05-13T00:15:18Z

hadarvc
May 13, 2026
Author

No problem whatsoever. I'll run the git version tomorrow. May 12, 2026 7:12:25 PM dawsers ***@***.***>:

…

Thank you. That is exactly what I needed. The problem now is we don't know what version of scroll the stack trace corresponds to. I tried compiling several versions from around May 1st, which is the date of the crash, but I haven't been able to find anything useful (the addresses don't correspond to those builds). So I am going to need to ask you to install the latest *git* version, write down which version hash you are running, make it crash, and produce the same information you wrote above (stack trace from coredumpctl). Maybe that will get us closer to the problem. I am sorry this is becoming a lot of work for you. Thank you. — Reply to this email directly, view it on GitHub[#261 (reply in thread)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/BGF44FKRCD3G47ACMIB3DOD42OVU3AVCNFSM6AAAAACYHCSTL6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBZG44TEMQ]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/BGF44FNPV73A6V7TKEIMGLL42OVU3BFCNFSM6AAAAACYHCSTL6WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBAHLYFJTSMVQXG33OUZQXK5DIN5ZA.gif]

0 replies

Regular Crash #261

Uh oh!

Uh oh!

hadarvc Apr 26, 2026

Replies: 5 comments · 19 replies

Uh oh!

Uh oh!

dawsers Apr 26, 2026 Maintainer

Uh oh!

dawsers May 12, 2026 Maintainer

Uh oh!

hadarvc May 12, 2026 Author

Uh oh!

dawsers May 12, 2026 Maintainer

Uh oh!

hadarvc May 21, 2026 Author

Uh oh!

Uh oh!

dawsers May 21, 2026 Maintainer

Uh oh!

hadarvc Apr 26, 2026 Author

Uh oh!

hadarvc Apr 29, 2026 Author

Uh oh!

hadarvc May 9, 2026 Author

Uh oh!

hadarvc May 13, 2026 Author

hadarvc
Apr 26, 2026

Replies: 5 comments 19 replies

dawsers
Apr 26, 2026
Maintainer

dawsers May 12, 2026
Maintainer

hadarvc May 12, 2026
Author

dawsers May 12, 2026
Maintainer

hadarvc May 21, 2026
Author

dawsers May 21, 2026
Maintainer

hadarvc
Apr 26, 2026
Author

hadarvc
Apr 29, 2026
Author

hadarvc
May 9, 2026
Author

hadarvc
May 13, 2026
Author