FYI, I started to fix a medium size folder which contains approx 680k tracks.
As you can see, songkong keeps crashing randomly. This did happen not only to bigger folders, but also almost every time I ran a fix on smaller (monthly) folders. I had to start the job again and again.
On very strange thing I did notice is that between first crash, and the next run, songkong usually runs a 0 track analysis, like you can see it in the following screenshot :
As you can see, it firstly loaded 19047 tracks, then crashed.
Next time I ran it, same folder, it loaded 0 tracks
I has to start the job one more time in order to get it to start loading tracs again, and it crashed one moe time after loading 58141 tracks.
I can tell you this is no memory issue, nor is it a docker container remaining drive space issue, as I did allocate it 500GB.
I believe we could take this as an opportunity to dig the logs and try to fix this random crash issue once for all, make songkong more rock solid and stable
By the way, I like how the logs did change, they are more readable, and I also like how the general songkong.log (of the docker) displays the processed folders :
I think this log should be used for the lambda users, it would be nice to add a few things here like:
Loaded folder /album_Folder/
Identified : /album_folder/
Unidentified : /Album_folder/
Rename and Moved to /Album_Folder/ -> Destination folder
Just my two cents