->toolkit::error console do you have a stack trace in about:crashes to point us to?
Created attachment 437049 [details] test case for this issue Test case , open it and press ctrl+shift+j wen load , or open your error console and them open the test case.
confirmed here on OS X 10.6.3 Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:126.96.36.199) Gecko/20100401 Firefox/3.6.3 ID:20100401064631 Didn't get a crash stack though. Thanks for filing this.
Flock Browser 2.5 crashes too on similar situation http://www.flock.com/
Seeing same stack on Win 7: http://crash-stats.mozilla.com/report/index/bp-164b34d3-6bea-4e96-880e-7dfdb2100405 Hang and eventual crash on 10.6, but no reporter catching the crash there.
The testcase is just code that asks the JS engine to fill up memory, and the crash is just operator new saying we're out of memory. Avoiding OOM crashes is bug 427099, bug 516518, bug 70821, or bug 482143. We're generally not bothering to fix the crash locations one at a time.
I figured it was just hammering the console with text, and the stack trace indicated it was failing on new operator. We can leave this open until that's fixed in the other referenced bugs. thanks Jesse.
The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed. If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.
I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console. If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid. Do not push that work onto the bug reporters. (It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify. But that is the ONLY situation where it is okay.) (I'm going to have to do this in two steps because of the way the "change several bugs at once" form works. Apologies for the extra bugspam.)
The Error Console feature was removed entirely from the tree in Bug 1278368 and the bugzilla component is now being removed. We’ve migrated bugs that seem to also affect the Browser Console into the devtools component, please move this over if it was missed.