Crash on Volume Analyze

[malkierian]

Had this happen 3 times (two times, for some reason, it had the same log ID), and I couldn't quite understand what the criteria were. First two times, it was analyzing a bunch of tracks I had that were 15-25 minutes long, and seemed to make it to around 18 tracks before crashing (because there were 36, and it finished the other half the next time, despite crashing again), then a third time when I had it analyzing 300 normal-length tracks, as it got to around track 200.

Log IDs:
45AF579D (large tracks)
45AF9D47 (normal tracks)

[PetrCBR]

Thanks. Will be fixed in next build.

[jimbob_sf]

I just saw this in 2113. The date on this post is 6/10. Was this targeted to be fixed in 2113?

I selected about 100 tracks and ran Analyze Volume. It crashed the first time and then I ran it again and it didn't. The interesting thing about the second time: It didn't return a track volume for all of them. I had to select a few at a time and repeat Analyze Volume.

The log ID from the crash got cleared from the clipboard before I could paste it. The log would have come around 8:30 am pacific time (GMT-8) on 6/30.

[PetrCBR]

No, check new 2114 (already available to download).

[teodore]

yes
now for the moment no problem to scan with 2114
goog job