Files
oak-gpui/crates
Thorsten Ball 8524e87319 linux/x11: Do panic when unmapping/destroying of X11 window fails (#13262)
We saw this panic come up:

```
called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: UnknownError })
core::panicking::panic_fmt
core::result::unwrap_failed
<gpui::platform::linux::x11::window::X11Window as core::ops::drop::Drop>::drop
core::ptr::drop_in_place<gpui::platform::linux::x11::window::X11Window>
core::ptr::drop_in_place<gpui::window::Window>
gpui::app::AppContext::shutdown
gpui::app::AppContext::new::{{closure}}
gpui::platform::linux::platform::<impl gpui::platform::Platform for P>::run
gpui::app::App::run
zed::main
std::sys_common::backtrace::__rust_begin_short_backtrace
std::rt::lang_start::{{closure}}
std::rt::lang_start_internal
main
__libc_start_call_main
__libc_start_main_impl
_start
```

I'm not sure where exactly that error comes from, except from the X11
stuff. So let's be defensive and log error and only then tear down
everything.

I _think_ that if the error is repeatable that means we won't close the
window but instead just log errors, but I do think that's better than
panicking right now.

Release Notes:

- N/A
2024-06-19 14:36:57 +02:00
..
2024-05-29 18:06:45 -07:00
2024-05-29 18:06:45 -07:00
2024-06-18 13:48:26 -06:00
2024-05-29 18:06:45 -07:00
2024-04-30 23:31:59 -06:00
2024-06-12 23:22:52 +03:00
2024-06-12 23:22:52 +03:00
2024-06-18 12:16:54 -07:00
2024-05-10 15:50:20 -06:00
2024-03-11 10:45:57 +01:00
2024-06-18 12:39:56 +02:00
2024-03-26 16:10:09 -07:00
2024-06-18 12:16:54 -07:00
2024-05-23 15:50:59 +02:00
2024-06-18 12:16:54 -07:00
2024-04-15 14:21:52 +02:00