New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash observed after restart driven by Windows Update #248

Closed
brogers5 opened this Issue Mar 13, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@brogers5

brogers5 commented Mar 13, 2018

Currently running the latest version (4.3.6643.23689) on Windows 10.0.16299.309. A crash was observed upon restarting after I had applied KB4088776 and KB4088785:

TracerX: Log file opened at 3/13/2018 7:18:24 PM. FullFilePolicy = Wrap, Use_00 = False, MaxGrowth = 1 MB, AppendIfSmallerThan = 0 1, initial size = 3.
19:19:11.992 Fatal SoundSwitch+ Exception Occurred Exception type: System.Threading.ThreadStateException
Message: Instance isn't set even after waiting 750 ms
Source: SoundSwitch
StackTrace:
at SoundSwitch.Framework.WindowsAPIAdapter.UnRegisterHotKey(HotKeys hotKeys) in D:\VS\SoundSwitch\SoundSwitch\Framework\WindowsAPIAdapter.cs:line 191
at SoundSwitch.Model.AppModel.SetHotkeyCombination(HotKeys hotkeys, DeviceType deviceType) in D:\VS\SoundSwitch\SoundSwitch\Model\AppModel.cs:line 374
at SoundSwitch.Model.AppModel.InitializeMain() in D:\VS\SoundSwitch\SoundSwitch\Model\AppModel.cs:line 206
at SoundSwitch.Program.Main() in D:\VS\SoundSwitch\SoundSwitch\Program.cs:line 130

I haven't been able to reproduce it on subsequent reboot attempts, so it might've been as a result of a one-off slow boot process. Perhaps the timer in question could use a little more wiggle room?
SoundSwitch-crashlog-13_3_2018.zip

@Belphemur Belphemur added the Bug label Mar 14, 2018

@Belphemur Belphemur closed this May 9, 2018

@brogers5

This comment has been minimized.

brogers5 commented May 12, 2018

Given that this was closed, I'm assuming no fix for this is planned? Just seems a bit odd considering it was previously acknowledged as a potential bug...

@Belphemur

This comment has been minimized.

Owner

Belphemur commented May 13, 2018

Unfortunately, I have no way of reproducing it. I don't consider it fixed, but more like can't reproduce.

Bug = Just acknowledging an issue arose.
Confirmed = Reproduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment