Version: unspecified (using KDE 4.5.0) OS: Linux The startkde script sets MALLOC_CHECK_ to 3 breaking eclipse (https://bugs.eclipse.org/bugs/show_bug.cgi?id=320487 - ok, eclipse's fault) but also slowing down performance by up to 30%, according to http://www.novell.com/support/viewContent.do?externalId=3113982&sliceId=1 (?). Also the comments in http://websvn.kde.org/branches/KDE/4.5/kdebase/workspace/startkde.cmake?view=markup suggest this should not have been enabled for a release in the first place. Reproducible: Always
Fixed
If it's fixed, then please, leave it RESOLVED / FIXED ;).
SVN commit 1170655 by dfaure: Let's try and remember to remove MALLOCK_CHECK_ on the next 4.x.0 release, up to now we forgot every time... CCBUG: 247398 M +1 -0 RELEASE-CHECKLIST WebSVN link: http://websvn.kde.org/?view=rev&revision=1170655
again, on 4.6 MALLOC_CHECK_ is set to 3 by startkde http://websvn.kde.org/branches/KDE/4.6/kdebase/workspace/startkde.cmake?view=markup looks as if this has been forgotten once again :(
Fixed again in 4.6 branch, revision 1217284
How about just keeping this disabled always, even in trunk? Developers who really want to debug memory issues can easily set MALLOC_CHECK_ on their own.
What about using "kde4-config --kde-version" to know if it is a development version? [lamarque@evolucao ~]$ kde4-config --kde-version 4.6.00 (4.6.0) If release number is above 50 it is a development version, right? We can something like: kde4-config --kde-version | perl -ne 'if (/(\d+)\.(\d+)\.(\d+)/) { if ($1 > 50) { print "development\n"; } else { print "production\n"}; exit 0; }'