tags 491671 moreinfo upstream unreproducible thanks Hi,
Monday 21 July 2008, [EMAIL PROTECTED] rašė: > Since the last upgrade of kdemultimedia-kio-plugins yesterday, Amarok has > started to randomly freeze on a track change. The track itself will play It is very unlikely kdemultimedia-kio-plugins could have caused this. It is even optional. Try removing it and see if it helps. > usually to completion but the UI will freeze and when the track finishes, > nothing else happens and no further songs are played. I tried really hard to reproduce this. Sorry, but no luck. UI does not freeze. I'll leave this bug as grave for now to increase its visibility but if nobody else complains severity will be downgraded. > I've included my dpkg.log along with three separate backtraces. Your log shows that none of Jul 20 upgrades are directly related to this bug. > The freeze is most definitely reproducible. > All I have to do it start > Amarok and next "Next Track" a number of times and eventually it will > freeze. Normally, Amarok likes to freeze around about the time when it > gets to the end of the playlist that I started with. That is, I start > Amarok with the playlist track1, track2, track3 saved from a previous > session then add tracks 4-7 for example either manually or as a dynamic > playlist. Once Amarok gets to the end of the previously saved playlist > (track3) it is very likely to freeze from then on. Very often it will > freeze on track4 but not always. I could not reproduce either freeze or crash by following these instructions. But my CPU is single core. Random nature of these crashes suggest that: 1) you have problem with RAM. 2) there is a race condition which cannot be easily reproduced on single core systems. Hence you could try booting the kernel with 'nosmp' option and try to reproduce. Or you could also try to move away amarok configs and try to reproduce: $ mv ~/.kde/share/config/amarokrc ~/.kde/share/config/amarokrc~ $ mv ~/.kde/share/apps/amarok ~/.kde/share/apps/amarok~ > The above method is what I used to get > the backtraces. It would help a lot if you installed amarok-dbg and ran: gdb amarokapp ... (reproduce the crash) ... (gtb) thread apply all bt .. post backtrace .. and installed valgrind and run: valgrind --num-callers=50 amarokapp (amarok runs with huge slowdown) ... (reproduce the crash)... ... post backtrace (double free references etc.) ... -- Modestas Vainius <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part.
