I encountered a segfault during messing around with multiple windows.
The most stable way I found to reproduce it is:
run Verso
press new window button
after new window spawned, press it again on the first window. wait for the 3rd window.
close one of the last two windows with system close (not from verso-panel)
It seems it's something with wayland. (my system is an Ubuntu fork, wayland, plasma 6)
==160743== Process terminating with default action of signal 11 (SIGSEGV)
==160743== Access not within mapped region at address 0x17C
==160743== at 0x766A885: ??? (in /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.22.0)
==160743== by 0x766A9F4: ??? (in /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.22.0)
==160743== by 0x766C449: wl_proxy_marshal_array_flags (in /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.22.0)
==160743== by 0x766CF5E: wl_proxy_marshal_flags (in /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.22.0)
==160743== by 0x8D42367: ??? (in /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0)
==160743== by 0x8D2A1D7: ??? (in /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0.0.0)
==160743== by 0x7694BC: _ZN4core3ptr83drop_in_place$LT$glutin..surface..Surface$LT$glutin..surface..WindowSurface$GT$$GT$17h8172f748c57bb4b5E.llvm.18333104610557856462 (in /home/mikopet/Git/verso/verso/target/release/verso)
==160743== by 0x769C78: <hashbrown::raw::RawTable<T,A> as core::ops::drop::Drop>::drop (in /home/mikopet/Git/verso/verso/target/release/verso)
==160743== by 0x77198C: core::ptr::drop_in_place<core::option::Option<verso::verso::Verso>> (in /home/mikopet/Git/verso/verso/target/release/verso)
==160743== by 0x776837: verso::main (in /home/mikopet/Git/verso/verso/target/release/verso)
==160743== by 0x79F905: std::sys_common::backtrace::__rust_begin_short_backtrace (in /home/mikopet/Git/verso/verso/target/release/verso)
==160743== by 0x7B78F7: _ZN3std2rt10lang_start28_$u7b$$u7b$closure$u7d$$u7d$17hc583dbad078eb90aE.llvm.5640221289294703489 (in /home/mikopet/Git/verso/verso/target/release/verso)
I encountered a segfault during messing around with multiple windows.
The most stable way I found to reproduce it is:
It seems it's something with wayland. (my system is an Ubuntu fork, wayland, plasma 6)
valgrind.log