Thursday, 5. October 2006, 19:25:51
As some of you might know, I had been running a SUSE installation on my machine - and I am using the past tense, since most packages have been (re)compiled locally and updated manually. I consider this to be a GNU/Linux installation "based on" SUSE 9.3. Still, I occasionally use Yast to update packages I am less interested in being "up-to-date" (SUSE is unbearably slow at updating packages!).
Well, a few days ago I decided to update Firefox (in case you wonder why I am less interested in being up-to-date on that one: this is my private machine, it's already enough to have Firefox installed at all), and used Yast to update it to 1.5.07 - as it was offered for download.
All went well - except for the little detail that the SUSE team must have been on crack when they decided to ship the Firefox update with debug turned on

Now I start Firefox and first am greeted with tons of debug lines about registering some components, then some
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp, line 1252
GFX: dpi=96 t2p=0.0666667 p2t=15 depth=24
++WEBSHELL == 1
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsPermissionManager.cpp, line 632
++DOMWINDOW == 1
++DOMWINDOW == 2
++WEBSHELL == 2
++DOMWINDOW == 3
++DOMWINDOW == 4
and some
###!!! ASSERTION: Should have the pref service here: 'mSysPrefService',\
file nsSystemPref.cpp, line 611
Break: at file nsSystemPref.cpp, line 611
###!!! ASSERTION: Potential deadlock between Monitor@8c629c0 and Lock@9303940: 'Error',\
file nsAutoLock.cpp, line 302
Break: at file nsAutoLock.cpp, line 302
Finally, when quitting Firefox, we close with
GC Cache:
hits: 144 30 47 25 83 13 14 7 0 3
hits: 366, misses: 168, hit percent: 68.539326%
JS engine warning: 24 atoms remain after destroying the JSRuntime.
These atoms may point to freed memory. Things reachable
through them have not been finalized.
nsStringStats
=> mAllocCount: 12139
=> mReallocCount: 1943
=> mFreeCount: 12137 -- LEAKED 2 !!!
=> mShareCount: 13731
=> mAdoptCount: 1641
=> mAdoptFreeCount: 1597 -- LEAKED 44 !!!
Update:MozillaFirefox - MozillaFirefox: Use optimized build
The previous MozillaFirefox update was errnously compiled with "debug" enabled,which caused slow downs and did an excessive amount of logging.