That's a "regression" due to bsmedberg's fix in bug 375710. The debug message has not been removed on checkin.
I was going to point at bug 375710 comment 100 saying it should only show up for people who explicitly turn on a debugging pref, but it turns out the debugging pref only affects dump() used in a DOM context (window.dump()). JS components dump() is enabled all the time and this really should be removed. We should also file a bug to "fix" dump() in JS components to prevent this confusion in the future, one of - make it obey the pref - make it debug-build-only if pref too hard - rename it to avoid confusion over behavior differences (print?)
Filed bug 379797 on the dump() confusion.
Created attachment 264010 [details] [diff] [review] Remove the dump() line Seeking review, should we want to take this patch for a respin of the release.
Comment on attachment 264010 [details] [diff] [review] Remove the dump() line We'll need to land this on MOZILLA_1_8_BRANCH as well as the release branch.
Comment on attachment 264010 [details] [diff] [review] Remove the dump() line approved for 126.96.36.199, a=dveditz for release-drivers Could also use debug() instead of dump() if you want to leave these in in the future.
Checked in on MOZILLA_1_8_BRANCH: Checking in nsDefaultCLH.js; /cvsroot/mozilla/toolkit/components/nsDefaultCLH.js,v <-- nsDefaultCLH.js new revision: 188.8.131.52; previous revision: 184.108.40.206 done
Fixed in version 220.127.116.11pre (20070604)