-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"malloc(): memory corruption (fast)", followed by hard lock #4039
Comments
By the way, I only ever play local tracks. |
It took 3 days for it to reoccur. Again, the failure to play happened on the first attempt to play a track after resuming from sleep. I could navigate clem just fine, even though it failed to play. I could also clear the playlist, but upon dragging and dropping a folder of tracks from my file manager (Thunar) into the playlist, the status in the bottom left was stuck at "Loading tracks 0%" with the throbber going continuously. The menu remained responsive, but when I clicked on one of the tabs, clem locked up. This happened at the "10:41:23.368 DEBUG SongLoader:226" line in the log. The malloc error occurred a couple of dozen lines above it. This time, I got a backtrace, and went up the stack one frame at a time. Not really sure what to do in gdb that would help: https://gist.github.com/mspacek/71e4a42f3c3905281f48 According to gnome-system-manager, clem had used about 2300 seconds of CPU time over those 3 days. This was with Version 1.2.1-123-gfde4586 from Dec 20th. |
Another 3 days, another hard lock, but this time, the error message was the previous fastbin one:
Strangely, clem ran fine for another day after the above message showed up in the log. Hard lock happened somewhere near the end of the log, which is followed by a backtrace: |
My latest reported error is from these last few lines in the log:
I noticed this after resuming from sleep. I also noticed that the tray icon has gone blank. This has happened occasionally in the past. Otherwise, clem continues to work fine (for now), even after another couple of suspend/resume cycles I did as a test. |
Still getting |
Note that this also seems related: https://code.mythtv.org/trac/ticket/10201 I might try setting the MALLOC_CHECK_ environment variable myself. Or, maybe it's time to upgrade from Xubuntu 12.10. |
I'm still having stability issues with the latest clementine, built from git with debug symbols, on Xubuntu 12.10 amd64, as reported earlier:
https://code.google.com/p/clementine-player/issues/detail?id=3483
After leaving clem running (though not necessarily playing) for a day or two, at some point, usually after resuming the system from sleep, I hit play or double-click a track in clem's playlist, and nothing happens. The play icon remains clickable, the stop icon remains disabled, the track position indicator doesn't move, and music doesn't play. At least this time I got this error:
*** glibc detected *** /usr/local/bin/clementine: malloc(): memory corruption (fast): 0x00007fffa00085e1 ***
The full log is here: https://gist.github.com/mspacek/3907d42e9f5d857f689f
Unfortunately, that doesn't come with a datetime stamp in the log, so I'm not entirely sure if it showed up before putting the system to sleep, or some time after waking it up (perhaps when clicking play unsuccessfully?). Sometimes clem remains responsive. I can navigate the menu, and I think even the library. Album artwork messages show up in the log as I'm scrolling the library. But the next time I hit a play control, clem locks up. Nothing shows up in the log. gdb doesn't detect anything. I have to kill clem manually. No backtrace to be had.
This was version 1.2.1-106-ga43116b from around Dec 12, pulled from the old google code site. Previously, as noted in the google code bug report above, instead of the malloc memory corruption error, I'd get a "invalid fastbin entry (free)" error, so it seems something's changed since at least May 2013. Also, previous logs of mine have included "usbmuxd_listen: ERROR: usbmuxd was supposed to be running here...":
https://code.google.com/p/clementine-player/issues/attachmentText?id=3483&aid=34830012000&name=clem6.log&token=hI1HdiW1RcwdinhF6ml4ukhKD5g%3A1387572393886
This usbmuxd error is referenced in a recent clem stability bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=967287
I don't have any other stability problems on this system, and it's gone through rigorous testing with memtest, so I doubt it's a hardware problem.
I've re-cloned from the new github repo, and am now testing version 1.2.1-123-gfde4586. I'll report when I get the hard lock again, hopefully get the same error, and maybe a better idea of when exactly it occurs in the sequence of events.
The text was updated successfully, but these errors were encountered: