Bug 118727 - Juk crashes on startup due to glibc memory error
Summary: Juk crashes on startup due to glibc memory error
Status: RESOLVED WORKSFORME
Alias: None
Product: juk
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-20 17:26 UTC by Fabio Junior Sabai
Modified: 2006-01-13 01:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Junior Sabai 2005-12-20 17:26:26 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Compiled From Sources
Compiler:          gcc-3.4.5 
OS:                Linux

Well, every time I upgrade my KDE juk fails. I am tired of this. This time, the crash occurs just when juk is lanched. The only output is: 

kio (KDirLister): +KDirLister
kio (KDirListerCache): +KDirListerCache
kio (KDirWatch): Can't use FAM (fam daemon not running?)
kio (KDirWatch): Available methods: Stat
*** glibc detected *** double free or corruption (out): 0x0831cec8 ***
juk: ERROR: Communication problem with juk, it probably crashed.

Ignore about fam, because when it's running the crash still happens.

kde was compiled from source, using gcc-3.4.5 with glibc-2.3.5.

I don't have any idea to do for fix it. Please help me!

Fabio Junior Sabai

Ps.: My english is not perfect.
Comment 1 Scott Wheeler 2005-12-20 17:49:13 UTC
Did you also upgrade your compiler recently?  Things like this usually happen after upgrading GCC without upgrading C++ libraries (such as taglib or libtunepimp).
Comment 2 Thiago Macieira 2005-12-21 02:12:57 UTC
Can you valgrind JuK? Or run it in gdb and give us the backtrace of the moment glibc shows that error message?
Comment 3 Michael Pyne 2005-12-21 02:26:22 UTC
If it is memory corruption valgrind would be the most useful by far.  gdb is likely to be unable to determine the correct backtrace.

At least this is judging from my investigations into the last JuK bug revealed by the glibc memory corruption monitor.
Comment 4 Fabio Junior Sabai 2006-01-13 01:13:48 UTC
Well, I upgraded libtunepimp and libmusicbrainz and now juk works fine. Thanks all.