Songkong never finishes Fix Songs Macbook Pro M1

[chrisG81]

Hello,
very often Songkong seems to never finish Fix Songs on my Macbook Pro (M1). I already deleted the Database. This had no effect.

Any idea?

[paultaylor]

Hi, thanks for the reports

FixSongsReport238 worked okay

From the logs I can see there was a few timeouts for FixSongsReport239 about 12:50, and then nothing much happened for the next three hours until you cancelled

But one thread was hanging onto a connection to wikipedia that never seemed to complete

12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.SocketDispatcher.read0(Native Method)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:47)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.NioSocketImpl.tryRead(NioSocketImpl.java:256)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:307)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:346)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:796)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.net.Socket$SocketInputStream.read(Socket.java:1099)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:489)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:483)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1461)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1066)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.io.BufferedInputStream.fill(BufferedInputStream.java:291)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.io.BufferedInputStream.read1(BufferedInputStream.java:347)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.io.BufferedInputStream.implRead(BufferedInputStream.java:420)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.io.BufferedInputStream.read(BufferedInputStream.java:399)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:827)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:759)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1690)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1599)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:531)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: java.base@21.0.1/sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:307)
12/02/2024 14.11.30:CET:MonitorExecutors:outputTraceForThread:SEVERE: app//com.jthink.songkong.analyse.musicbrainz.Wikidata.convertWikiDataUrlToWikipediaUrl(Wikidata.java:50)

And I think this is what prevented it from completing. I’m not sure if the issue is caused by wikipedia or your internet connection failing but it doesn’t really matter, SongKong should eventually give up but does not seem to be.

So you eventually cancelled, and then cancelled the report creation as well. It would be good if you could retry and if it seems to hang again only cancel the processing but let the report creation complete so then you can see what the problem folder is, I can see from the logs that there are just 12 songs not processed

12/02/2024 15.11.54:CET:FixSongsReport:writeToBothLogs:SEVERE: Report:239:SongsLoaded:479
12/02/2024 15.11.54:CET:FixSongsReport:writeToBothLogs:SEVERE: Report:239:SongsDone:467

Then I have raised an issue to add a timeout to the wikipedia connection and that should prevent problem occurring

[paultaylor]

Wikipedia issue fixed in new release.

SongKong 10.3 Blur released 4th March 2024

We are pleased to announce SongKong 10.3 Blur is released 4th of March 2024 [blur] This major release has the following new features: Auto Edit Manual editing is useful for making changes to one album, but what about if we need to make an edit to many albums, then for this we have the new powerful Auto Edit tool. This actually comprises three tools Capitalizer , Find and Replace and Trim , and any or all of these tools can be applied to multiple fields in one go. See here for full details …