v0.11.1, 0.12.0-alpha.0 freezes on startup
Opened this issue · 2 comments
Describe the bug
SuperConductor freezes on startup
To Reproduce
Steps to reproduce the behavior:
- Install SuperConductor 0.12.0-alpha.0 or v0.11.1
- SuperConductor opens the view and freezes
Expected behavior
SuperConductor should not freeze.
Screenshots
Desktop (please complete the following information):
- OS: Windows 11
- Version 0.12.0-alpha.0
Additional context
I'm attaching my SuperConductor folder:
SuperConductor.zip
I did not check versions prior to v0.11.1.
Deleting the contents of the Projects subfolder didn't change anything, SuperConductor still froze. Deleting the entire SuperConductor folder didn't help either. I tried disconnecting my Stream Decks, didn't help either.
STDOUT from SuperConductor.exe on startup:
2023-06-28T13:05:35.143Z [electron] info: Starting up...
2023-06-28T13:05:35.160Z [electron] info: Internal HTTP API available at http://localhost:5500/api/internal
Checking for update
ThreadedClass (4600) Skipping exit handler registration as no exit handler is registered
MidiInWinMM::initialize: no MIDI input devices currently available.
2023-06-28T13:05:36.800Z [electron] warn: TSR TSR is not initialized yet
2023-06-28T13:05:36.809Z [electron] info: TSR Initializing device casparcg0 (6008) of type CASPARCG...
Update for version 0.12.0-alpha.0 is not available (latest version: 0.12.0-alpha.0, downgrade is allowed).
checkForUpdatesAndNotify called, downloadPromise is null
I'm suffering the same issue with v0.11.1 from the releases published here on github
OS: Windows 11 22H2 (OS Build 22621.1192)
I'm suffering the same issue with v0.11.1 from the releases published here on github
OS: Windows 11 22H2 (OS Build 22621.1192)
I have been able to narrow this down to a problem with node-hid library taking veeeery long to return a list of attached devices. Unfortunately, the API is not async, so it locks up the main thread until it returns. On the other hand, I have not been able to replicate this issue after rebooting. Do you have anything that could mess with HID or USB stack somehow? For me, one possible culprit is OpenRGB, because that's something that I've installed recently.