Lost settings on abnormal shutdown

Michael Liddle michael at liddle.net.nz
Sat Oct 17 11:29:29 UTC 2009


Mark Kretschmann wrote:
> Well, no, that would be a kludge I think. I would prefer to solve it
> properly. My idea is using multi-threading for saving the playlist,
> and also storing it in the database, which may be faster than storing
> as XSPF.

Yes, well this obviously makes much more sense :)

> That's definitely not normal. When you log out from your desktop
> (let's say KDE), the desktop sends all applications the TERM signal,
> then waits a few seconds, then sends KILL to apps that haven't shut
> down yet. TERM does the same as a normal shutdown (Quit). So, what
> happens here is either your Amarok takes too long to shut down, or
> your desktop does something incorrectly.

Desktop is KDE. See below for timing and behaviour on TERM...

> As for Amarok, start it with "amarok --debug --nofork" from the
> terminal once. It will print tons of information. Click "Quit" in
> Amarok, and then check if you can see anything weird in the debug
> output (it provides timing information too).

Under a "normal" shutdown, App::~App() (which I presume corresponds to
quit?) takes around 1.4s, although I'm not sure how different this would
be after swapping bits of the application out of memory etc... (I have a
pretty old laptop, with only 512M RAM).

Anyway, when I send a TERM signal to the process (`killall amarok`)
App::~App() was not called at all (or at least it doesn't show up in
that debug output). Should/could it be?

Thanks,
Mike.

> 




More information about the Amarok mailing list