SuperConductor Resource Refresh Crash (v0.11.0-alpha.2) about superconductor

[nytamin]

Thanks for reporting this!

I haven't seen this particular issue, could you help me with troubleshooting this?
First, could you try running the software using command-line, to see if there are any clues in the console?
How to do it:

1. Open a command-line console (type "cmd" when in start menu)
2. In the console, run %USERPROFILE%\AppData\Local\Programs\superconductor\SuperConductor.exe
3. Try to make the program crash
4. If there are any clues in in the terminal, please paste them here.

Other things that might give some clues are:

• if you could record your screen when it crashes
• if you could export the project (Home-tab -> Project -> Export to file)? You could share it to me privately ([email protected]) if you'd like.
• Try installing an older version of SuperConductor, and see if you can figure out at which particular version it starts to crash?

[Tvgeekfromthelate2000s]

Thanks for reporting this!

I haven't seen this particular issue, could you help me with troubleshooting this? First, could you try running the software using command-line, to see if there are any clues in the console? How to do it:

1. Open a command-line console (type "cmd" when in start menu)
2. In the console, run %USERPROFILE%\AppData\Local\Programs\superconductor\SuperConductor.exe
3. Try to make the program crash
4. If there are any clues in in the terminal, please paste them here.

Other things that might give some clues are:

• if you could record your screen when it crashes
• if you could export the project (Home-tab -> Project -> Export to file)? You could share it to me privately ([email protected]) if you'd like.
• Try installing an older version of SuperConductor, and see if you can figure out at which particular version it starts to crash?

I followed the instructions, and this is what came out of the command prompt:

2023-03-26T19:03:37.865Z [electron] info: Starting up...
2023-03-26T19:03:37.876Z [electron] info: Internal HTTP API available at http://localhost:5500/api/internal
Checking for update
Update for version 0.11.0-alpha.2 is not available (latest version: 0.11.0-alpha.2, downgrade is allowed).
checkForUpdatesAndNotify called, downloadPromise is null
ThreadedClass (7407) Skipping exit handler registration as no exit handler is registered

MidiInWinMM::initialize: no MIDI input devices currently available.

2023-03-26T19:03:38.869Z [electron] warn: TSR TSR is not initialized yet
2023-03-26T19:03:38.877Z [electron] info: TSR Initializing device casparcg0 (5936) of type CASPARCG...
2023-03-26T19:03:38.883Z [electron] info: CasparCG casparcg0: Sideload connection initialized
2023-03-26T19:03:39.045Z [electron] info: TSR Device casparcg0 (5936) initialized!
[15120:0326/150404.904:ERROR:node_bindings.cc(145)] Fatal error in V8: Reached heap limit Allocation failed - JavaScript heap out of memory
[15120:0326/150404.905:ERROR:crashpad_client_win.cc(815)] not connected

[nytamin]

Thanks for the logs, there must be an out-of-memory issue somewhere..

Let's continue the troubleshooting, here are a few more questions for you:

• Did you pinpoint the issue to appear in a certain version? 0.11.0-alpha.2?
• Does the crash still happen if you close Caspar and then do the refresh?
• About how many items do you have in your Caspar media and templates folder?

[Tvgeekfromthelate2000s]

Strangely enough, it doesn't crash when CasparCG is open, but rather when the "scanner" is open (I'm using v2.3.3 of CasparCG in case if you're wondering). Of course, nothing shows up in the 'Available Sources" when the scanner isn't open, so it would still be useless on my end, but it still works without it.

And again, the version that the crash occurs in is v0.11.0-alpha.2 (I checked multiple times).

I'm not sure how many items there are in my media folder, but there is a lot. Even with this in mind, i had no issues with v0.10.5, so I'm not exactly sure what's going on.

Edit: I went back to v0.10.5, and found out that I have 1461 pieces of media (including the templates and the media that was pre-installed).

[nytamin]

@Tvgeekfromthelate2000s Thanks for the help in troubleshooting the issue! Could you give the latest prerelease (v0.11.0-alpha.3) a go, it has a fix that I hope will fix your issues.

(It's a temporary fix that limits the number of thumbnails to 500, so you might loose thumbnails for some of the media. Eventually we'll implement a proper fix that handles an unlimited amount of media/thumbnails, but this should do for now.)

[Tvgeekfromthelate2000s]

I'll gladly give it a shot, and I'll let you know if it works.

[Tvgeekfromthelate2000s]

Nope.

[nytamin]

Huh, that's unfortunate.

Let's try some other things, if you don't mind?

1. Could you check what the size of these folders are?
   YOUR_CASPARCG_FOLDER/_media
YOUR_CASPARCG_FOLDER/pouch__all_dbs__
2. Another test:
   a. Close media-scanner
   b. Delete the folders mentioned in step 1
   c. Restart media-scanner
   d. Wait a bit while it scans everything.
   e. Does SC still crash?
3. What happens if you reduce the number of media files, does that avoid the crashes? At what number of files (approximately) does it crash or not?

[Tvgeekfromthelate2000s]

Huh, that's unfortunate.

Let's try some other things, if you don't mind?

1. Could you check what the size of these folders are?
   YOUR_CASPARCG_FOLDER/_media
YOUR_CASPARCG_FOLDER/pouch__all_dbs__
2. Another test:
   a. Close media-scanner
   b. Delete the folders mentioned in step 1
   c. Restart media-scanner
   d. Wait a bit while it scans everything.
   e. Does SC still crash?
3. What happens if you reduce the number of media files, does that avoid the crashes? At what number of files (approximately) does it crash or not?

Unfortunately, neither of those worked. And frankly, Idk what's going on.

Also, I apologize for taking so long to respond.

[nytamin]

Unfortunately, neither of those worked. And frankly, Idk what's going on.

Also, I apologize for taking so long to respond.

Thanks for taking the time anyways!

I've drafted a new feature where we'll change how the resources are refreshed, here: #143.

Since it'll drastically change "everything" in how the resources are handled internally, there's a good chance it'll solve your issues too.
I can't give a time-plan for when that'll be implemented though.

[Tvgeekfromthelate2000s]

Unfortunately, neither of those worked. And frankly, Idk what's going on.
Also, I apologize for taking so long to respond.

Thanks for taking the time anyways!

I've drafted a new feature where we'll change how the resources are refreshed, here: #143.

Since it'll drastically change "everything" in how the resources are handled internally, there's a good chance it'll solve your issues too. I can't give a time-plan for when that'll be implemented though.

Alright, I'll be on the lookout for when that gets implemented. Thank you for the help so far.