Yes, the problem still occurs on Lucid (Beta 2). I can reliably produce a segmentation fault by double-clicking on a midi file, allowing it to play to the end and start the next (non-midi) track, and then double- clicking on a midi file. The segfault happens as this second midi file starts to play.
I could not produce a segfault if I running Ryhthmbox under valgrind memcheck, although the valgrind log (attached) does show lots of invalid reads and writes associated with WM_ParseNewMidi. ** Attachment added: "valgrind log (gzipped)" http://launchpadlibrarian.net/44705658/valgrind_lucid_beta2.log.gz -- Rhythmbox crashes towards end of midi file https://bugs.launchpad.net/bugs/468371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
