Version: (using KDE Devel) Installed from: Compiled sources Compiler: GCC 3.3.5 64-bit X86_64 OS: Linux When Noatun is invoked with a file that it does not know how to play, it gets very confused. The artsd and noatun processes begin using almost all CPU time, and the noatun process grows larger and larger. To reproduce, launch noatun with a filename that noatun cannot play, such as an empty file. On the console, I get the following message repeated over and over again. artskde: KDE::PlayObject: destroyed artskde: KDE::PlayObject: destroyed noatun: [bool Engine::open(const PlaylistItem&)] No playobject for 'file:///home/velma/x' I have Noatun get up to dock into the system track, and quitting Noatun from the context menu of its system-tray icon does not actually stop Noatun. Instead, it keeps running and consuming more and more memory. The case of trying to play an empty file is kind of silly, and sometimes people will accidentally try to play a file in Noatun. In my case, I appear not to have FLAC support for Noatun, but the .flac extension was associated with Noatun.
Please try playing the file with "artsplay" (on the command line). This should help determine whether the problem lies in arts or noatun.
I can confirm this with noatun 3.5 branch/ from today. Additionally, it causes multiple artsd crashes, as artsd is (presumably) restarted each time it dies. Neither artsplay nor kaboodle demonstrate this behaviour.
mETz: this is why we cannot do the "play the next file if this one fails" thing.
Hmm? This works fine here, and if it does not then it's always the kde playobject crashing for me, especially on shoutcast streams that are offline. Btw, this is kind of fixed in make-it-snow, it crashes way less often and if it does it's also in kde playobject (I vote to get rid of this anyway and use arts playobject directly)
noatun has not been part of the KDE 4 release and is no longer maintained. KDE now offers Dragon as a video player and JuK as a music player. Additionally, other popular KDE players have been ported to KDE 4, such as Amarok or Kaffeine. If this issue is still applicable to KDE 4 applications, please add a comment or file a new report. For more information, see http://websvn.kde.org/?view=revision&revision=718046