Amarok collection scanner is crashing during collection rescan

[Dave Fear]

my music collection is around 6-7000 tracks and is located partly on an ext3 filesystem on my ubuntu edgy desktop and partly on my server connected via mounted fuse-ssh connection.

I'm using Amarok 1.4.4 from kubuntu.org on ubuntu edgy.

crashes @ ~88-99% when trying to rescan collection.

An error dialog was displayed, could only read the top half because the bottom half was off the bottom of the screen and couldn't be moved up. it said something about "collection scanner stopped due to too many errors during scanning" or something like that.

[Caroline Ford (secretlondon)]

Package: amarok 2:1.4.4-0ubuntu1
ProcCmdline: /usr/lib/amarok/amarokcollectionscanner --nocrashhandler -p -s

The crash report is a seg fault.

[Ari Niemi (ari-niemi)]

I noticed the same problem with Edgy, Amarok 1.4.3 and TagLib 1.4.4. Screen shot included

[Vlad Socaciu (vladsocaciu)]

during a collection rescan, Amarok sais it crashed and made this error report, but it went on with scanning and worked fine after that.

one reason for the crash might be that i deleted a folder and added another one during the scan. but scanning lasts a few minutes for my >8500 collection so chances are slim.

[Freddy Martinez (freddymartinez9)]

Some issues you may be having are due in part to fuse and another user had altered the collection while scanning. I'm not sure this is a bug in amarok, but a result of user changes. Do you have any steps to where I can reproduce this bug?

[Vlad Socaciu (vladsocaciu)]

"Do you have any steps to where I can reproduce this bug?" Well, I was
rescaning the 8500 songs library (i didn't notice the update button at that
time). about one minute after moving some files inside the big collection
folder (i was moving it during the rescan) i got that crash message. but
everything was ok after that, and the folder i had moved was included in the
database, so that was probably not the reason for the report. i don't know
what more "steps" i could give you. anyway, it wasn't a big problem at all,
just a wrong, confusing message.

On 12/22/06, Freddy Martinez <email address hidden> wrote:
>
> Some issues you may be having are due in part to fuse and another user
> had altered the collection while scanning. I'm not sure this is a bug in
> amarok, but a result of user changes. Do you have any steps to where I
> can reproduce this bug?
>
> ** Changed in: amarok (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> Amarok collection scanner is crashing during collection rescan
> https://launchpad.net/bugs/72390
>

[Andrew Ash (ash211)]

It sounds like Vlad's bug resulted more from messing with the folders while Amarok was scanning, but Dave's has more to do with remote files than changing the files themselves. As long as you stay away from the folders while they're being scanned, you should be good.

Dave, can you still replicate this crash?

[Ari Niemi (ari-niemi)]

I removed the two real media files, which emerged in the collection scan report (see my post and screen shot above), from my collection folder. After that the scan was successful and it didn't crash anymore.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

appears to also be a dupe of 61188

[Launchpad Janitor (janitor)]

[Expired for amarok (Ubuntu) because there has been no activity for 60 days.]