[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 104503] amarok hangs freeze when editing file tag
From:       Gilles Schintgen <gilles () vonet ! lu>
Date:       2005-05-11 20:09:56
Message-ID: 20050511200956.4938.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=104503         




------- Additional Comments From gilles vonet lu  2005-05-11 22:09 -------
On Wednesday 11 May 2005 21:46, Mark Kretschmann wrote:
> Using -fomit-frame-pointer is very bad mojo. You win basically nothing, and
> earn meaningless backtraces instead. Sorry, but that's ricer++.

You're right and I'm thinking about taking it out. I'll probably compile all 
of KDE with the proper settings for debugging on my new PC. After all, decent 
backtraces are much more useful than 0.1% performance or something like that. 
But for now I won't recompile everything. An athlon 700 can be slow at 
times...


Anyway, I can now reproduce the following behaviour most of the time:
1. start amarok
2. open tag editor for some file
3. do MusicBrainz lookup
4. modify some tags (only necessary if MusicBrainz wasn't successful)
5. try to save the modifications
6. Result: amarok immediately freezes completely.
The backtrace is always the same as in my previous comment.

The changes are committed to the file.
[prev in list] [next in list] [prev in thread] [next in thread]