SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Songkong stops in an endless loop


My internetspeed is in my opinion no problem, until now I never had any issues with reliability.
I will see if i Have somewhere a 2TB external disk and try what you suggested, but I am confident my network is OK.

Hi, its not your external internet access that is a problem it’s your local network.

In fact the issue may not be the local network itself the issue might be with device connected to the network where the files are stored.

If you can find your external drive I am very confident this will work for you.

I am copying the files to an extern ssd, will take forever​:notes::stuck_out_tongue:I will let you know iif this works, Of course thismis not a real solution, but it is worth trying as an experiment

Yes, but of course if it takes a long time to copy the files even locally that does seem to indicate that maybe there is a problem with disc access on your server. Did you say it was an Antipodes Audio server, if so might be worth rebooting and making sure dont use it for playback of music or anything else whilst attempting this.

Audio servers are designed for quiet, reliable playback of music but they are low powered audio appliances not general high-performance NAS boxes, is the internet connection wired or wireless?

Hi Paul,
I transfered most of the files from the server to an extern SSD. Result : it stopped workin after a short time

. The app was unresponsive so I had to forcequit, afterwords I made the report for you.

It hadn’t stopped working, it was doing stuff and then you cancelled

01/05/2026 14.21.48:CEST:SEVERE: ++SaveStart:64417:/Volumes/Extreme SSD/MusicFiles/Alleluia/09 Recit_ Sub tantae Virginis tutela.flac
01/05/2026 14.22.39:CEST:WARNING: G1456:Foldername:Andreas Ottensamer Romanza 2025 24-96:isPartOfMultiDisc:false:Warning memory was low so cancelling processing for this group and trying to allocate more memory:Java heap space
01/05/2026 14.22.39:CEST:SEVERE: ++SaveStart:63346:/Volumes/Extreme SSD/MusicFiles/Akademie für Alte Musik, Berlin/A Vivaldi Grand Tour, Disc 1/02 Concerto for oboe, strings & continuo in C major (_L'Olimpiade_)_ II. .flac
01/05/2026 14.22.39:CEST:SEVERE: User Cancelled Task
01/05/2026 14.22.39:CEST:SEVERE: Adding Error:Unable to match song to MusicBrainz:/Volumes/Extreme SSD/MusicFiles/Andreas Ottensamer Romanza 2025 24-96/108 Clarinet Sonata in D Major - II  Andante quasi adagio.flac:org.hibernate.exception.JDBCConnectionException: could not extract ResultSet
java.lang.RuntimeException: org.hibernate.exception.JDBCConnectionException: could not extract ResultSet

Can you please:

  • Restart SongKong
  • Run Admin:Empty Database
  • Start Fix Songs on Volumes/Extreme SSD

and then just leave it to run or actually fail with error.

1java

Support files uploaded, I am really sorry for both of us, it costs a lot of time for you. For me no problem because I am a retired MD an I have plenty of free time. But first tonight: F1 Miami :wink:
Regards,
Mike

Thanks for your patience, its okay, worth getting to the bottom of these problems to make better product.

So interestingly in this case the memory problem is not caused by a large SongSaver queue here and there were no Save errors so far.

image

I think this particular failure is caused by parallel matching of multiple box sets. So the workaround would be to try increasing the max memory allocated again to 8gb - close SongKong, then you can use this plist file I previously uploaded and then restart SongKong and try again.

Info.plist (3.0 KB)

Hopefully the increased memory will be enough to avoid the memory issue that should be a temporary blip that will resolve once the folder has completed processing.

Unfortunately although the logging shows when the OutOfMemory ocurred that does not neccessarily show the process that is hogging the memory just the process that attempted to get the extra memory when there was none. In fact I should improve the logging to help identify likely cause of problem by taking a snapshot of all process running at the time, and grabbing a snapshot of the objects currently grabbing the most heap memory.

Hi, have you been able to retry with the increased memory?

Goodmorning Paul,

Finally it succeeded!. I uploaded the support files some minutes ago.
Thanx for your help, it would be handy if the app also works on my network attached SSD.
One other question: there are a lot of albums in my library that are split in two or more albums. This was repaired by Roon, but I do no longer use Roon, so I am searching for an app which can merge two or more albums into one, without merging the flac files. Dit you ever consider building an app which can do this automatically, all the apps I tried cannot do this without retagging the album by hand.
Best regards,
Mike

Great, looked at your report and things looking pretty good.

SongKong generally groups songs by folder and only allows a match if all songs in folder can be matched to one album. But if songs have already been split into multiple folders or are already matched to multiple albums within one folder it is a bit harder to fix with Fix Songs task. However the Match to One Album task can be applied to one folder at a time to find albums that match all songs in folder and then fix. Although if the album is not in MusicBrainz, Discogs or AcoustId there is little that can be done.

The Inconsistencies section of the report shows potential metadata issues, but it would help me if you could give me some specific examples of albums split into two or more albums so I can see exactly what you mean.

So the increased memory when matching locally allowed Fix Songs to work for you, this shouldnt be necessary but there are some edge cases where this can happen. I’ve replicated the OutOfMemory issue locally by limiting memory to 500mb on my 20,000 song library and am looking for ways to better handle this type of issue.

There was no errors at all during this last run but when running against your networked files the underlying issue is with either your server or your local network as demonstrated by the super slow saving of files and save errors. This manifested as an OutOfMemory error because my save queue didn’t set an upper limit to its size. Now I have fixed this for next release and this should prevent the OutOfMemory error however this is not going to solve the underlying issue of your network/server being slow/unreliable.

To solve the saving file over the network problem it might be worth you getting some advise from Antipodes about this.

I have now released new version of SongKong with significanlty better memory handling.