#467 crash on start in tiling WM (4K resolution)

[Yuri Pankov]

Fuse dies on start with weird backtraces when launched in a tiling WM (i3), likely when the window is resized to take the full width/height of 3840x2160. It looks like it doesn't happen with a lower resolutions though (e.g. 1024x768). While I have found the workaround of using the floating mode for Fuse window, it took me quite some time to figure it out.

Running 1.5.7 on FreeBSD. An example of backtrace (doesn't look related at all):

Reading symbols from /usr/local/bin/fuse...
[New LWP 101516]
[New LWP 101789]
Core was generated by `fuse'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00000000002528c2 in readbyte (address=16384) at memory_pages.c:397
397       return mapping->page[ address & MEMORY_PAGE_SIZE_MASK ];
[Current thread is 1 (LWP 101516)]
(gdb) bt
#0  0x00000000002528c2 in readbyte (address=16384) at memory_pages.c:397
#1  0x00000000002e1279 in z80_do_opcodes () at ./z80/opcodes_base.c:307
#2  0x000000000024cd6f in main (argc=1, argv=0x7fffffffeb18) at fuse.c:199

Or it could be getenv() in libc, or some other arbitrary place in the system.

[Gergely Szasz]

Hello Yuri,

Which UI compiled in?
GTK2/GTK3/SDL/X11?

How can you manage to "window is resized to take the full width/height of 3840x2160."? This is a WM feature?

Now only SDL UI has a "fullscreen" mode, when SDL try to set a "good" resolution and put the fuse scaled window (1x, 2x, 3x or 4x) on the center of the screen.

The backtrace is so weird, but X11 async behaviour can cause some weird thing...