segfaults on Linux

[acarl005]

Hello. We're seeing segfaults originating from global-hotkey in our logs. Here is a stacktrace:

OS Version: Linux 6.2.0 (39-generic)
Report Version: 104

Crashed Thread: 3499986

Application Specific Information:
Fatal Error: SIGSEGV / SI_KERNEL / 0x0

Thread 3499986 Crashed:
0   libc.so.6                       0x7f562b63eab3      __run_exit_handlers (exit.c:72)
1   libc.so.6                       0x7f562b6e1c7f      __libc_pause (pause.c:29)
2   libc.so.6                       0x7f562b63eccf      exit (exit.c:141)
3   libX11.so.6                     0x7f562a2622a2      _XDefaultIOError (XlibInt.c:1317)
4   libX11.so.6                     0x7f562a26221f      [inlined] _XAllocID (xcb_io.c:626)
5   libX11.so.6                     0x7f562a26221f      _XAllocID (xcb_io.c:623)
6   libX11.so.6                     0x7f562a264c02      _XIOError (XlibInt.c:1548)
7   libX11.so.6                     0x7f562a267b74      _XEventsQueued (xcb_io.c:444)
8   libX11.so.6                     0x7f562a25a706      XPending (Pending.c:55)
9   libc.so.6                       0x7f562b6e1c7f      __libc_pause (pause.c:29)
10  warp                            0x56166297bac9      global_hotkey::platform_impl::platform::events_processor
11  warp                            0x561662980c85      std::sys_common::backtrace::__rust_begin_short_backtrace::<T>
12  warp                            0x56166297e65f      std::thread::Builder::spawn_unchecked_<T>::{closure#1}::call_once::{shim:vtable#0}
13  warp                            0x5616631be274      std::sys::unix::thread::Thread::new::thread_start
14  libc.so.6                       0x7f562b68f6b9      start_thread (pthread_create.c:444)
15  libc.so.6                       0x7f562b68f3cf      [inlined] create_thread (pthread_create.c:240)
16  libc.so.6                       0x7f562b68f3cf      create_thread (pthread_create.c:240)
17  libc.so.6                       0x7f562b71e11f      clone3 (clone3.S:81)

Unfortunately, that's all the info we have on the issue currently. We're not sure how to reproduce this.

[amrbashir]

that's unfortunate, without a reproduction, I can't really investigate