Hi all,

I keep getting hangs when trying to edit track information with MusicBrainz. Music play also hangs. All I can do is killall amarokapp and start it again. Strangely, the information is saved. But I can only edit one song at a time and amarok always hang

Are you seeing that?

I\'m using amarok 1.3.6, gentoo, kernel 2.6.13.4, kde 3.4.0, gcc (GCC) 3.4.2 20041025 (Gentoo Linux 3.4.2-r3, ssp-3.4.1-1, pie-8.7.6.5).

Thanks for any info.

Yes, I had the same problem with vers 1.31 & 1.3.5. The problem is that
amarokapp chews up all the available memory and swap space. I have
a half-gig of each and it gets used up.

My guess is that mysql is doing some sorting--tho I can\'t imagine what.

In my case I compiled amarok without mysql nor postgresql setup. So I\'m using sqlite.

I didn\'t notice the increased memory usage. But I didn\'t test it anymore

Ah, btw, I forgot to say that I\'m using xine engine. I don\'t know if it matters.

I hope someone can help us.

My solution was to uninstall amarok-scripts. Since doing this, I haven\"t seen the problem again.

As an aside, I notice that the application requires an inordinate amount of memory--mostly virtual(141M)--to run. I love the functionality, but I am concerned with the memory bloat. Especially since I usually am running amarok in the background while I\'m working on something else.

I am now searching for standalone programs to emulate the functionality and then use a lighter weight player.

joeymac wrote:

As an aside, I notice that the application requires an inordinate amount of memory--mostly virtual(141M)--to run. I love the functionality, but I am concerned with the memory bloat. Especially since I usually am running amarok in the background while I\'m working on something else.

I am now searching for standalone programs to emulate the functionality and then use a lighter weight player.

From what I\'ve noticed, the main memory usage of amaroK is the playlist, particularly when it contains a large number of tracks. Using smart playlists in dynamic mode dramatically reduces memory required.

Thanks for the tip!

This forum rocks!

I\'ve seen the same behaviour (1.3.6) too but I can\'t really figure out how to get more detailed/useful information to include in a bug report. amarokapp goes off into a endless loop after trying to save a tag via \"right click->edit track information\". But this behaviour is a bit random and doesn\'t happen with all mp3s. As said above the only way out is to kill amarok (the tag is saved though).

joeymac, It doesn\'t really matter how much virtual memory an application consumes. That\'s nothing to worry about, you should look at what\'s actually in memory (rsize/residental memory).

Note: Tagging FLAC files is inherently slow, due to the the madness of its metadata format. Very slow.

So, if you\'re working with FLAC files, the delay is normal.