Repository navigation
Windows: Quit leaves the process and output window running #5
Description
Found while testing the MSI from PR #4's release run (9d2637f, self-contained build) on Windows 11.
Steps: tray panel → Quit → confirm.
Expected: the process exits.
Actual: the log shows CursorFollowWin exiting., and the tray icon and hotkeys go away. But the process and the CursorFollow Output window stay alive. It was still hung after 25 s and had to be killed with Stop-Process.
ExitApplication (CursorFollowWin/App.xaml.cs) gets past _hotkeyService.Dispose() and _trayIcon.Dispose(). The hang is in one of _outputWindow.DisposeCapture(), AppLog.Shutdown() or Current.Exit(). That's not confirmed yet, because there was no dump tooling on the test machine.
Open question: is this a regression from PR #4? That PR switched publishing to WindowsAppSDKSelfContained=true. A framework-dependent dev build (dotnet build, F5) would tell us. Check that first.
Everything else in the smoke test passed: install with no UAC, tray icon, panel, live output, About shows 0.5.1, publisher shown as Logan Rupe, and a clean uninstall.
Activity
fix(win/app): close every window before Application.Exit so Quit exits
fix(win/app): close every window before Application.Exit so Quit exits
LoganRupe commentedon Oct 10, 2026
Fixed in 2f14bf9 (PR #6, merged to main through #4). ExitApplication now closes the Settings, panel and output windows before Application.Exit(). With Settings open, Exit had been closing only some windows, and the one it skipped kept the message loop alive. Not a regression from the self-contained build: the framework-dependent Debug build hung the same way. Verified on Debug and the installed MSI. Quit exits in about 0.15 s, with or without Settings opened.
fix(win/app): close every window before Application.Exit so Quit exits
fix(win/app): close every window before Application.Exit so Quit exits