Crashing during library scan

[paulmorabito]

Hi, I'm running gaseous via docker (latest version) on Unraid. I did not use the template on this site and instead set it up myself. I have a library of about 30k roms. I am noticing during a library scan, my whole Unraid locks up. (CPU hits 100%). Either gaseous eventually crashes or I can get a command line and stop the container manually. There is nothing in the logs around when this happens that looks out of the ordinary. I know this is not much to go on so if there is anything I can do to further troubleshoot then please let me know.

[michael-j-green]

Hi @paulmorabito; can you which processes on your Unraid host are taking up so much CPU? Is it high CPU, or high IO wait?

Anything in the Gaseous logs?

With a library that large, have you considered breaking it up into smaller libraries and adding a few libraries at a time?

[paulmorabito]

Hi @paulmorabito; can you which processes on your Unraid host are taking up so much CPU? Is it high CPU, or high IO wait?

Anything in the Gaseous logs?

With a library that large, have you considered breaking it up into smaller libraries and adding a few libraries at a time?

The CPU definitely spikes and nearly all cores are at 100% so the Unraid web UI is unresponsive. I can SSH in but there's a lot of lag so I did a "docker stop" on the container and after a couple of minutes, it stopped. There's nothing in the logs for gaseous apart from what looks like normal library scanning related activity. I thought maybe the docker.img was filling up but this was also not the case and RAM usage didn't spike either.

I will check re: processes next time this happens.

I have added a lot of libraries (one per platform) as my filesystem layout is different to the desired structure of gaseous. Is there a way to scan per library? I could only see the library scan job which scans all of them.