Rhythmbox crashes towards end of midi file

[Mike Fisher]

Binary package hint: rhythmbox

Rhythmbox crashes 2-3 seconds before the end of a midi file, or when switching from one midi file to the next in my Music directory.

ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 11:18:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.12.5-0ubuntu4
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f0e56efbeda: mov 0x8(%rbx),%rdx
 PC (0x7f0e56efbeda) ok
 source "0x8(%rbx)" (0x0000111b) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 realloc () from /lib/libc.so.6
 WM_ParseNewMidi () from /usr/lib/libWildMidi.so.0
Title: rhythmbox crashed with SIGSEGV in realloc()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug report is public and visible to everyone but I noticed that it has an attachment named 'CoreDump.gz'. It is possible that this contains sensitive information so I've set it back to private.

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate (av=0x7f0e571f0e40) at malloc.c:5087
_int_free (av=0x7f0e571f0e40, p=0x28fa890)
_int_realloc (av=0x7f0e571f0e40, oldp=0x28d9790,
*__GI___libc_realloc (oldmem=0x28d97a0,
WM_ParseNewMidi (

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Mike Fisher (mfisheresq)]

Since reporting this bug, I have installed several updates recommended by Update Manager. The bug no longer happens every time I play a midi file. It only crashes if I play a succession of different files. However, I think I managed to crash rhythmbox in the attached valgrind log.

[William (condonwe)]

I registered on Launchpad specifically to report this bug. Rhythmbox crashes when finishing one MIDI file and starting another. It does not crash when finishing one MIDI file if the file immediately after that is an OGG; it does not crash when finishing an OGG file even if the file immediately after that is a MIDI. When I launch Rhythmbox from the command line and view Standard Output at a crash, it reads, "Segmentation fault".

This problem has affected me since upgrading from Jaunty to Karmic.

[Mark (pilota51)]

I have this same problem. When I have MIDI files in my playlist, Rhythmbox asks to search for a suitable plugin (audio/riff-midi) and doesn't find any. MIDI files still play fine, it's only when switching directly from one MIDI file to another that it crashes. I can switch from a MIDI file to an MP3 or OGG file and back to a MIDI file without it crashing. It's not much of a deal with my large randomized playlist of 99% non-MIDI files, but still an annoyance when I want to specifically listen to more than one MIDI file.

I haven't used Rhythmbox much until recently, so I don't know how long this issue has been around. I have Ubuntu 9.10 Karmic (kernel 2.6.31-19) with packages up-to-date.

[Pedro Villavicencio (pedro)]

Is somebody still getting this on Lucid? there's no reports stating that on latest release there. May you please test with lucid and comment back? Thanks in advance.

[Mike Fisher (mfisheresq)]

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.

[Sebastien Bacher (seb128)]

The valgrind log shows invalid write in wildmidi code, it lacks debug symbol though, maybe you could add a midi example to the bug?

[Mike Fisher (mfisheresq)]

midi example attached, as requested...

[Sebastien Bacher (seb128)]

Thank you for providing the requested informations

[Steve (sckaplan)]

I the same problem of Rhythmbox crashing near the end of playback of a midi file. Any fix as yet?

[Mike Fisher (mfisheresq)]

This bug seems to be fixed in Ubuntu 10.10
At least, I was unable to reproduce it.

[Mathieu Cossette (mcossette)]

I'm able to produce a bug when reaching end of song im on Ubuntu 13.10 with all the latest updates

reaching end of song makes Rhythmbox crashes

[Mathieu Cossette (mcossette)]

And here is the report in Terminal ... with -d debug from Rhythmbox

** (rhythmbox:6309): CRITICAL **: Converting of type 'void' is not implemented
**
ERROR:../../gi/pygi-argument.c:1903:_pygi_argument_from_g_value: code should not be reached
(21:41:18) [0x7fc788004730] [rhythmdb_process_one_event] rhythmdb.c:2500: processing RHYTHMDB_EVENT_ENTRY_SET
Abandon (core dumped)

[Bret Curtis (psi29a)]

I cannot reproduce this bug on 13.10, either using my own midis or the ones provided here.

I cannot get Rhythmbox to crash with midi using wildmidi backend on x86_64-linux-gnu.

[Bret Curtis (psi29a)]

Going to close this with fixed, as this is old, no one is responding and when I tested, I couldn't reproduce it.