[BUG] UI fails to render after sleeping/waking up laptop

[bbishop-neovest]

Component

Lite

Performance Monitor Version

2.11.0

SQL Server Version

SQL Server 2022

Windows Version

Windows 11 Enterprise 25H2

Describe the Bug

When running Performance Monitor Lite and closing the laptop lid, upon reopening the laptop and logging back in, the UI has disappeared; however, notification messages continue to pop up with metrics and alerts that change over time, indicating that the application is still running. When I try to rerun the UI, I get an empty window:

Steps to Reproduce

1. Start Performance Monitor Lite
2. Verify expected monitoring behavior
3. Lock the screen or close the laptop lid
4. Open the laptop lid and unlock the computer
5. Verify that the running application is now missing from your Windows desktop and that the running application's icon is missing from the Windows task bar
6. Verify that you still receive alert notifications
7. Reopen Performance Monitor Lite and verify no UI elements appear in the application window.
8. Close the Performance Monitor Lite window.
9. Reopen Performance Monitor Lite and verify expected behavior.

Expected Behavior

When unlocking the lock screen, the application should appear on the Windows desktop and should be represented in the Task Bar. The application should display the information from the tab that was open before the computer was locked.

Actual Behavior

After unlocking the lock screen, the UI was completely missing but the application was still running.

Error Messages / Log Output

No WARNING or ERROR messages were added to the log files; instead, there are Collector INFO messages throughout the problem time window.

Screenshots

No response

Additional Context

No response

[erikdarlingdata]

Thanks for the detailed report — the steps and the "notifications still fire but the window is gone" detail were exactly what pinned this down.

There were actually two problems stacked together:

1. Blank window after wake. WPF renders its UI on the GPU, and a sleep/wake (or RDP reconnect) can tear down that GPU surface in a way WPF doesn't recover from — leaving the window alive (so notifications keep firing) but unable to repaint. Fixed by switching both apps to software rendering, which removes the GPU dependency. Your charts are unaffected because they're drawn on the CPU via SkiaSharp, not the GPU path.

2. Window disappears from the taskbar. Windows turns the lid-close into a "minimize," and the minimize-to-tray feature then hides the window — with no automatic way back on wake. A new resume handler now brings the window back from the tray when you wake/unlock, if it was on-screen before sleeping (a window you deliberately sent to the tray is left alone).

This is merged to dev (#1053) and will ship in the next release (2.12.0). If you're able to run a dev build once it's available, I'd appreciate confirmation that the sleep/wake cycle behaves for you — but the change is well-grounded in Microsoft's own guidance for this WPF render-thread failure class.

[bbishop-neovest]

Happy to test a dev build when ready.

[erikdarlingdata]

@bbishop-neovest it will be in tonight's nighlty build if you want to test early.

[bbishop-neovest]

Approximately what time (Eastern)?

Also, the customer service in this place is stellar!

[erikdarlingdata]

The nightly kicks off at 06:00 UTC, so right around 2:00 AM Eastern. The release artifacts usually show up a few minutes after that once the build and packaging finish — so grab it any time after ~2:15 AM ET and the #1050 fix will be in it.

And thank you — much appreciated! 🙏

[bbishop-neovest]

@erikdarlingdata I uninstalled the release build, downloaded the zipped nightly build of PerformanceMonitorLite-2-11-0-nightly.20260604, and ran the PerformanceMonitorLite executable directly from the unzipped folder. The bug still exists, so I am unable to verify the fix. Additionally, simply minimizing the application to the tray removes the application from the tray altogether (per your bug write-up) and causes the same UI rendering problems.

I also note that the build number is 2.11.0 in the "About" window. I expected to see the full nightly build number but perhaps the build process only pulls the major/minor/release identifiers from the full build number?