[BUG] Issues after booting from sleep mode

[Rajdave69]

Version

6.0.5

Windows Version

Version 22H2 (OS Build 22622.601), Win 11 pro

Actual Behaviour

The app will be buggy in various ways

• The GUI will stop working but hotkeys continue, no toasts work and opening the GUI from app drawer just wont work.
• The app will completely stop working
• A memory leak will cause the app to eat a ton of ram (look at image)
• The toast location changes to another position in another monitor

One of the four above things happens to me most of the times after starting my PC from the sleep state after ~16 hours.

Expected Behaviour

App to function normally

Reproduction Steps

Go to power options and click sleep
after a while start the device from sleep again

Log

Couldn't get the log since i had to restart my PC forcefully due to the memory leak

[radj307]

This is a high severity bug and is being treated as high priority. The behaviour you described (except for 4) is definitely consistent with a memory leak.

Having a log file would make diagnosing this issue much easier. Putting my computer to sleep for 16 hours to test this is just not possible for me.

Prior to putting your PC to sleep while volume control is running again, please do the following:

1. Enable all log levels (including TRACE), and ensure logging is enabled
2. Disable run at startup

When your computer wakes up, kill the volume control process if necessary, open the file explorer, and navigate to the directory where the log file is stored (This will be in the same directory as the EXE (portable version) or in C:\Users\<USERNAME>\AppData\Local\radj307\VolumeControl (if you used the installer)). The log from the most recent run will be there even if you had to reboot the system.

Regrading actual behaviour 4, that is likely caused by the window size changing when the computer goes to sleep. In which "direction" did the notification window move (left/up/right/down/multiple)? For the notification window to retain its relative position, it has to update its position every time the window changes size. Knowing which direction the window drifted would help determine what is going wrong.

[Rajdave69]

Regarding 4, here is the position I set and the position it goes to (screenshot includes both monitors)

Did the step 1 and 2 and will monitor for any similar issues.

[radj307]

By the looks of things, it appears my hypothesis about the cause of actual behaviour 4 was correct. When the computer wakes up, the window has to do a lot of extra work to update itself for the new state of the system. WPF may be doing this extra work in an unexpected order (such as if the window state being changed halfway through rather than right away), causing the window to drift.

I did some light testing of the memory leak bug and it doesn't appear to happen naturally - something about the computer going to sleep & waking up is the most likely cause. I now have a Windows 11 Pro 22H2 VM installed so I can start further testing soon.

Of note is that none of these issues seem to happen when hibernating instead of sleeping.

[radj307]

Are you still experiencing this with the newest version?

[Rajdave69]

will check, downloaded 6.5.1 now

[teadrinker2015]

I don't know if this is related: the installer-version's GUI won't show up after a reboot, even manually close-reopen. But a standalone version would. (also, dosen't show up notifications on volume adjustment, but I have a shortcut to or manually toggle it, so it's rather trivial)