GNOME Bugzilla – Bug 349992
Crashing while initializing music database
Last modified: 2006-08-04 22:54:25 UTC
Distribution: Ubuntu 6.06 (dapper) Package: rhythmbox Severity: Normal Version: GNOME2.14.2 0.9.4.1 Gnome-Distributor: Ubuntu Synopsis: Crashing while initializing music database Bugzilla-Product: rhythmbox Bugzilla-Component: general Bugzilla-Version: 0.9.4.1 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: During first start, one was asked to enter the PATH to your saved music. Once entered, the program starts indexing all the files in the database. After about 300 initialized songs, rythmbox crashes and "forgets" the indexing it just did. If I let rythmbox start indexing the files and then quit it before it crashes, it will save the new index. Next time I start it, it will go on indexing from the new starting point until it crashes. So to finish indexing rythmbox, I have to quit it about every 300 new files and open it again. I did not test, wether it happens if only mp3 files are in the PATH of my saved music, because sometimes I have rar archives and mp3 files together. Steps to reproduce the crash: 1. Get an amount of music stored in several folders - perhaps with other files, eg. RAR between them 2. Let rythmbox start indexing these files (should be enough files... prob. > 1000) Expected Results: How often does this happen? reproduceable Additional Information: Using OSS Driver instead of ALSA Debugging Information: Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227859232 (LWP 6213)] [New Thread -1269793872 (LWP 6226)] [New Thread -1243362384 (LWP 6217)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 69987
Thread 1 (Thread -1227859232 (LWP 6213))
-- Echte DSL-Flatrate dauerhaft f\xFCr 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl ------- Bug created by bug-buddy at 2006-08-04 21:53 -------
The top ~15 frames of the stack trace look very similar to bug 343443, which also occurs while importing. I think we might be screwing up something with the gdk lock, but that's just a hunch. Can you get us another stack trace with the gtk debug info package (libgtk2.0-0-dbg) installed?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. The stacktrace actually is identical to the one in bug 346445. *** This bug has been marked as a duplicate of 346445 ***