Intermittent crashing when closing last window in context #3

sleen commented 2026年06月26日 15:32:48 +02:00

I've noticed a very strange issue where sometimes, when closing the last remaining window in a context, River itself will crash. Interestingly, this only seems to happen when closing the window with specifically a keybind. Manually running argenctl window close in a terminal window doesn't seem to trigger it.

So far I've only been able to reproduce this issue with foot(1), but it's possible it affects other applications too. I'm not sure if this is an issue on your side or elsewhere.

I've attached the log output below in case it's helpful. I'm running River 0.4.3, foot 1.27.0, and the latest master version of argen.

I've noticed a very strange issue where sometimes, when closing the last remaining window in a context, River itself will crash. Interestingly, this only seems to happen when closing the window with *specifically* a keybind. Manually running `argenctl window close` in a terminal window doesn't seem to trigger it. So far I've only been able to reproduce this issue with `foot(1)`, but it's possible it affects other applications too. I'm not sure if this is an issue on your side or elsewhere. I've attached the log output below in case it's helpful. I'm running River 0.4.3, foot 1.27.0, and the latest master version of argen.

pkap commented 2026年06月26日 18:49:36 +02:00

The log does not contain the stacktrace unfortunately. You could try to run river with -log-level debug or even better build river in debug mode (zig build -Doptimize=Debug). This should give us more information about the crash.

I think some river crashes have been fixed since 0.4.3. It would probably be easier to first see if the crash persists with river .0.4.5 or main.

The log does not contain the stacktrace unfortunately. You could try to run river with `-log-level debug` or even better build river in debug mode (`zig build -Doptimize=Debug`). This should give us more information about the crash. I think some river crashes have been fixed since 0.4.3. It would probably be easier to first see if the crash persists with river .0.4.5 or main.

sleen commented 2026年06月27日 13:41:35 +02:00

You could try to run river with -log-level debug or even better build river in debug mode (zig build -Doptimize=Debug).

Right, I forgot that was an option. I had to build with -Doptimize=Debug to get any information, but it seems like this is indeed fixed on the latest master for River. I didn't realize the version packaged for Alpine Linux was out of date.

> You could try to run river with -log-level debug or even better build river in debug mode (zig build -Doptimize=Debug). Right, I forgot that was an option. I had to build with `-Doptimize=Debug` to get any information, but it seems like this is indeed fixed on the latest master for River. I didn't realize the version packaged for Alpine Linux was out of date.