base::FileDescriptorWatcher::Controller::Watcher::~Watcher

[sentry]

Sentry Issue: NEXU-DESKTOP-PROD-19

EXC_BREAKPOINT / EXC_I386_BPT / 0x112697866: Fatal Error: EXC_BREAKPOINT / EXC_I386_BPT / 0x112697866
  File "immediate_crash.h", line 188, in base::FileDescriptorWatcher::Controller::Watcher::~Watcher
  File "file_descriptor_watcher_posix.cc", line 102, in base::FileDescriptorWatcher::Controller::Watcher::~Watcher
  File "file_descriptor_watcher_posix.cc", line 186, in base::FileDescriptorWatcher::Controller::~Controller
  File "unique_ptr.h", line 76, in ProcessSingleton::LinuxWatcher::SocketReader::~SocketReader
  File "process_singleton_posix.cc", line 561, in std::__Cr::__tree<T>::destroy
...
(13 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Send new issues to slack and github

[lefarcen]

Thanks for the automated crash report. This stack is landing in Chromium/Electron native teardown (base::FileDescriptorWatcher -> ProcessSingleton::LinuxWatcher::SocketReader), so from the first trace it looks closer to the Linux single-instance / socket-watcher path than to our TypeScript or renderer code.

Worth comparing with #1167 as well, since that one is another native socket-path crash rather than an app-level JS failure. If anyone can reproduce this outside Sentry, the most useful follow-up here would be the desktop version, Linux distro / session details, and whether it happens on startup, shutdown, or when launching a second instance. Because native main-process crashes can be uploaded on the next app launch, notes from the previous session are especially helpful here.

Join communities:

• Feishu: https://applink.feishu.cn/client/chat/chatter/add_by_link?link_token=90emc2e9-86cd-4723-b455-ca41b70f162d
• Discord: https://discord.gg/nexu