Closed KateReller closed 8 months ago
Issue appears to be caused by something failing inside of CoreAudio.AudioSessionManager2.RefreshSessions()
Will investigate.
Added a try-catch block around the CreateAndAddDeviceIfUnique
call within the AudioDeviceManager
constructor to log information about the offending device in 1e1bf1b5ddece929c490e834e940fafce44f0b7e. This should prevent the application from crashing (at least during initialization), but will also prevent whichever device caused the problem from being loaded. This is a worthy tradeoff since it wouldn't be possible to load that device anyway.
Pushing a new tag 6.6.4-rc1
for you to test, will provide an update shortly.
UPDATE: The test version is available here. See this wiki page for download instructions. Ignore the update prompt if it appears.
Let me know if the issue persists for you when using that version.
I do not see any issues with 6.6.4-rc1
. Here's the log files.
VolumeControl.log
However, I cannot recreate the issue on 6.6.3
anymore.
From the provided log file, it appears that the issue didn't occur at all that time. This isn't too surprising, especially if you rebooted the machine between attempts. These kinds of issues are fickle, as the cause is dependent on internal Windows processes, your specific setup, and any number of other external variables.
Nonetheless, it's still a bug, and a critical one at that. Thank you for reporting, the changes I implemented should prevent this from happening in the future.
Closing this as completed, the fix will be included in the next full release.
Version Number
6.6.3
File
Portable (VolumeControl.exe)
Windows Version
Modified Windows 11 (Atlas OS)
Actual Behaviour
When Volume Control launches, no hotkeys function. When opening the GUI, the taskbar icon appears but there's no window to be seen.
Expected Behaviour
Volume control should launch with hotkey functionality and with a GUI.
Reproduction Steps
No response
Log