Bug 140001 - Qutting Amarok after a manual stop causes Amarok to flood the system with amarokapp processes
Summary: Qutting Amarok after a manual stop causes Amarok to flood the system with ama...
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.4
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-13 01:40 UTC by Daniel Kao
Modified: 2008-06-25 11:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Kao 2007-01-13 01:40:50 UTC
Version:           1.4.4 (using KDE KDE 3.5.5)
Installed from:    Slackware Packages
OS:                Linux

Quitting Amarok after a manual stop (whether by "stop now" or "stop after current track") causes Amarok to spawn a bunch of amarokapp processes.

Steps to reproduce:
1. start Amarok
2. play a song in Amarok
3. stop the song
4. quit Amarok

This is reproduceable every time on my system, on 1.4.4 and on the SVN version I compiled today (1/12/2007)
Comment 1 Mathieu Havel 2007-01-19 20:24:51 UTC
Hi all,

I confirmed this bug which is really boring !
So amarok launches too many processes (and instances, ie. several amarok icons on the kicker), too hard to stop because it keeps launching the application, even after many killall commands !

This happened under same conditions than with Daniel Kao.

Please, fix the problem...

system : Kubuntu Edgy Eft.
Amarok : 1.4.4 (using KDE KDE 3.5.5), from Edgy repository

Mathieu
Comment 2 richlv 2007-01-22 09:18:44 UTC
are you using universal sidebar ? if so, the problem should be fixed in the next version (though amarok was simply restarting for those people, not flooding the system...)
Comment 3 Daniel Kao 2007-01-22 12:27:22 UTC
No, not using the universal sidebar, problem occurs independent of WM/DE.
I recompiled my xine-lib and it seems the crash doesn't occur with "stop now" anymore, though "stop after current" is crashes miserably.
So the problem might be with the way Amarok uses xine, or this is juse a xine bug. Though there's no other xine frontend I know of that does "stop after current".
Comment 4 Theofilos Intzoglou 2007-01-30 01:27:13 UTC
This is also happening here whenever amarok crashes. I'm using the xine engine too. This is in Gentoo running KDE 3.5.6 and amarok 1.4.4 (but it happened in 1.4.3 too). If there is any other info I can give you that will help this really annoying bug just ask. I'll be glad to be of help! :-)
Comment 5 Daniel Kao 2007-02-06 20:52:48 UTC
Problem still persists with Amarok 1.4.5 on KDE 3.5.5
this is what I get in the console:
amarok: [CollectionDB] track ended: file:///home/milkycow/secret.mp3
amarok: BEGIN: void EngineSubject::stateChangedNotify(Engine::State)
amarok:   [Moodbar] Resetting moodbar:
amarok: BEGIN: virtual void ContextBrowser::engineStateChanged(Engine::State, Engine::State)
amarok: END__: virtual void ContextBrowser::engineStateChanged(Engine::State, Engine::State) - Took 0.088s
amarok:   [Moodbar] Resetting moodbar:
amarok: END__: void EngineSubject::stateChangedNotify(Engine::State) - Took 0.11s
amarok: BEGIN: virtual void ThreadManager::Thread::run()
amarok: BEGIN: SqliteConnection::SqliteConnection(const SqliteConfig*)
amarok: END__: SqliteConnection::SqliteConnection(const SqliteConfig*) - Took 0.0019s
amarok:   [ThreadManager] Job completed: CurrentTrackJob. Jobs pending: 0
amarok: END__: virtual void ThreadManager::Thread::run() - Took 2.6s
amarok: BEGIN: virtual App::~App()
amarok:   [CollectionDB] track ended:
amarok:   [static void PluginManager::unload(Amarok::Plugin*)]
amarok:   [PluginManager] Unloading library: libamarok_void-engine_plugin
amarok: BEGIN: void Playlist::saveXML(const QString&)
amarok: END__: void Playlist::saveXML(const QString&) - Took 0.0012s
amarok: BEGIN: virtual ContextBrowser::~ContextBrowser()
amarok: END__: virtual ContextBrowser::~ContextBrowser() - Took 0.013s
amarok:   [virtual CollectionView::~CollectionView()]
amarok: BEGIN: virtual PlaylistBrowser::~PlaylistBrowser()
amarok: END__: virtual PlaylistBrowser::~PlaylistBrowser() - Took 0.00045s
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
amarok:   [MediaBrowser] having to remove 1 devices
amarok: BEGIN: void MediaBrowser::removeDevice(MediaDevice*)
amarok:     [MediaBrowser] remove device: type=dummy-mediadevice
amarok: BEGIN: void MediaBrowser::unloadDevicePlugin(MediaDevice*)
amarok: END__: void MediaBrowser::unloadDevicePlugin(MediaDevice*) - Took 0.00054s
amarok: END__: void MediaBrowser::removeDevice(MediaDevice*) - Took 0.0052s
amarok: BEGIN: virtual ScriptManager::~ScriptManager()
amarok: END__: virtual ScriptManager::~ScriptManager() - Took 0.0031s
amarok: BEGIN: virtual ThreadManager::~ThreadManager()
amarok:     [ThreadManager] Waiting on thread...
amarok:     [ThreadManager] Waiting on thread...
amarok:     [ThreadManager] Waiting on thread...
amarok: END__: virtual ThreadManager::~ThreadManager() - Took 0.0002s
amarok:   [static void PluginManager::unload(Amarok::Plugin*)]
amarok:   [xine-engine] xine closed
amarok:   [xine-engine] Scope statistics:
amarok:   Average list size: 69
amarok:   Buffer failure:    0%
amarok:   [PluginManager] Unloading library: libamarok_xine-engine
amarok: END__: virtual App::~App() - Took 0.56s

and then there's nothing after that, amarokapp starts flooding the system and I had to killall amarokapp
Comment 6 Michael Leupold 2008-06-15 15:18:19 UTC
comment from KDE bugsquad member

I can't reproduce this bug on 1.4.9.1. Can't check in Amarok 2 as the functionality doesn't yet work in trunk r820602.
Comment 7 Seb Ruiz 2008-06-25 11:07:30 UTC
can't reproduce either.