694927 - FF7 Crashing, locking up Mac, console=nsautoreleasenopool object x of class y autoreleased with no pool, just leaking

Status: RESOLVED WORKSFORME

(Core :: Widget: Cocoa, defect)

Description

[noneyabeeswx]

Attachment: Console Message Log Firefox nsautoreleasenopool - just leaking

FF 7.0.1 locks up my computer with no warning.  Usually the screen becomes totally unresponsive although the cursor still moves.  Sometimes I get spinning wheel, sometimes not.  Escape key no help, can't get anything on screen to work and am forced to do a hard shutdown with manual power button.  Waiting doesn't help either, even after 10 minutes or more if frozen this way it won't resolve.

I have attached a console message log showing all of the nsautoreleasenopool just leaking errors.  I've also attached a firefox crash report.  Actually, I don't see how to get the bug reporter to allow me to attach more than one file, so I've just attached the console message log.  Please email me at noneyabeeswx "at" gmail "dot" com or let me know how to send you the crash report (and I have a few other console message logs from different times showing this problem too).

Comment 1

[noneyabeeswx]

This is occurring on a macbook pro, intel core duo, OS X 10.5.8

Comment 2

[Matthias Versen [:Matti]]

did bug 634702 fixed this already ?

Comment 3

[noneyabeeswx]

If fixed, it wouldn't be happening now.  Something broke firefox 7 since then (I went from 3.6 directly to 7).  Bug 634702 refers to FF5 on OS X 10.6.  This is happening now on FF 7, OS X 10.5.  It also refers to "nsNativeThemeCocoa" - don't know if that string should appear in console if related to this current problem, but I found no matching string when checking console logs (system, console, and all messages). 

I found another bug report on this issue before posting this bug that was also marked resolved - clearly something is still triggering the problem and the problem is repeatedly locking up and crashing the entire computer.

Comment 4

[noneyabeeswx]

Attachment: Another example of huge numbers of console lines re nsautoreleasenopool

Comment 5

[noneyabeeswx]

Attachment: Another example

Comment 6

[noneyabeeswx]

Matthais, or anyone.... is this bug being worked on at all?

Comment 7

[Matthias Versen [:Matti]]

This bug is still unconfirmed and someone needs to confirm this report.
We have no other reports about this at the moment...

Comment 8

[Steven Michaud [:smichaud] (Retired)]

There isn't anywhere near enough information here to work with.

The _NSAutoreleaseNoPool() messages are just what they say -- leaks.  These (small) leaks won't by themselves cause crashes.

What we need are detailed, precise, steps to reproduce.

Comment 9

[Steven Michaud [:smichaud] (Retired)]

Furthermore, FF 7.0.1 is no longer the current version of Firefox.

Comment 10

[noneyabeeswx]

Well, that's quite the reply.  First, 7 WAS the most current version when I first reported the bug.  Second, I'm sure there are still quite a few people who are using v. 7.0.1, and will be for some time.  Third, it does the same thing with v 8.  I don't know about 9, because I don't know how to check for these sorts of errors on a PC, and for a little bit I'll be on a PC.  Tell me how to check, and I certainly will.

Next, if I didn't provide enough information to work with, how about you tell me what you need and how I go about finding it on my computer, instead of fluffing the problem off?  I'm not a programmer, I'm a user, trying to help you folks keep firefox working the best it possibly can.  As far as detailed precise steps to repeat the problem - launch firefox, and presto, those are the console error messages that appear.  That's all it takes to recreate the problem - launch firefox.  As to whether small leaks can cause crashes - perhaps I didn't word it the best possible, and should have said "hang."  Add up a bunch of small memory leaks, over time, and when you run out of available memory, the computer hangs to the point it's unusable, or it crashes, and either way you have to reboot.  If you are VERY lucky, just firefox hangs and one can force quit firefox and restart it - otherwise, the entire computer system hangs, and you are out of luck.

As to no other reports of this yet - I'm willing to bet that the majority of users don't have a clue to look in console error messages, and if they do, they've no idea what the error messages mean, and/or they don't bother to take the time and effort to figure out how to report bugs.  Replies such as yours certainly don't encourage us to take that time and effort either - that's how you lose people to other browsers.

Comment 11

[noneyabeeswx]

Oh, and in the meantime, since you guys didn't appear to be working on the problem at all, I THINK, but am not certain, that the add-on "session manager" which is used by, what, millions of people? may be responsible for these leaks.  So, try adding session manager to firefox, browse a bit, then restart firefox and have it load the previous browsing session, and see if you don't get these sorts of leaks spawned.  Frankly, it's a great add on and one of the reasons I stay with firefox - but if it is what's causing the problem, it won't be worth it.

Comment 12

[Rares Doghi, Desktop QA]

Closing this issue as WFM because no crashes have been reported in the last 6 months. We can reopen if the issue starts to reoccur.