You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows] Calling destroy() method is crashing the app and app is not responding anymore. #452
Closing as a duplicate of #478: destroy() on Windows hangs or takes seconds because the message loop is quit before the native window is destroyed. The workaround is in #478 (comment), and PR #590 fixes it.
Activity
Arley011 commentedon Jul 22, 2024
I also face this issue on version 0.3.9. And it happens in release build only, which is even more strange...
kibsoft commentedon Sep 20, 2024
For those looking for a solution, a workaround can be found here: #478 (comment)
In my case, I simply added
exit(0)when closing the app from the tray icon menu:windowManager.destroy().then((_) => exit(0));lijy91 commentedon Sep 21, 2026
Closing as a duplicate of #478:
destroy()on Windows hangs or takes seconds because the message loop is quit before the native window is destroyed. The workaround is in #478 (comment), and PR #590 fixes it.