Picard crashes when getting AcoustIDs

This was happening in 2.8.4 occasionally and restarting Picard solved it for some time but now after updating to 2.8.5 it seems to be happening more often. There is this album that Picard doesn’t like at all, it crashes always with a memory couldn’t be written error message, if I open Picard with -d, the first time the error stopped, the second time Picard hung forever and stopped responding and in the logs I only got in the last line

D: 10:00:35,970 acoustid\__init__._run_next_task:259: Starting fingerprint calculator 'C:\\Programas\\MusicBrainz Picard\\fpcalc.exe' '\\\\192.168.1.1\\f$\\Música\\Alan Menken\\(1992) Aladdin, Special Edition Soundtrack\\02. Legend of the Lamp.flac'

So it seems the error happened again but for some reason instead of crashing it just hung. By the way running fpcalc manually with each song didn’t crashed.

My first suspicion would be some issue with accessing the network drive. Because if I try to run fpcalc with a network path I cannot access it hangs like this while waiting to get something to read.

What happens if you run the following from a CMD prompt?

"C:\Programas\MusicBrainz Picard\fpcalc.exe" "\\192.168.1.1\f$\Música\Alan Menken\(1992) Aladdin, Special Edition Soundtrack\02. Legend of the Lamp.flac"
1 Like

Tried a bunch of times just in case and in all of them it was OK, I didn’t get any errors. I think network credentials are OK as I have 10 mounted shares that I access frequently, with 3 of them accessed all the time (in real time I mean).

Not sure really what the issue is. Maybe you are running with different user accounts or something?

As I understand it fpcalc just hangs there. Maybe try mounting your network drive as a proper drive (assigning it a drive letter), or move your files for tagging to the local disc.

The shares are mounted with their own drive letter, which is from where I drag&dropped the files in Picard. I don’t know why it shows in the log as if I loaded the files from the network path.
The weird thing is that it happens only sometimes, not always.

I just got the error message this time when launching picard with -d

La instrucción en 0x000001E2311FCD60 hace referencia a la memoria en 0x000001E2311FCD60. La memoria no se pudo written.

Haga clic en Aceptar para finalizar este programa
Haga clic en CANCELAR para depurar el programa

Btw, just tried with files in a local drive and I get the same behavior so it seems is not related to network shares.

S you get this error message when doing the scan (and fpcalc gets run)?

Yes, I only get the error msgs/crashes/hangs when getting the AcoustIDs. It happens both with network and local drives. It happens both with FLAC and MP3 files.

1 Like