Firefox Crash - No Script Update

[Plipp]

95% of the time that Firefox crashes, it restarts and brings me to a NoScript update page. Crashes happen ~80% of the time when I'm waking my computer up from sleep. I don't know if it's part of Firefox's updating process and it's just that NoScript updates so much more often than my other addons, that crashes result from sleep mode or what. Does anyone have insight to this?

[barbaz]

http://forums.informaction.com/viewtopi ... =7&t=18826 ?

[therube]

I noticed that (SeaMonkey) Aurora memory usage went to hell, so I went looking & the first thing I saw was YEINU: Your Experience Is Not Universal (even though it probably does not apply in my case .)

("Aurora is also using quite a bit more RAM then 2.23. 1.7 GB running 2.23 for a short while, then close down & doing nothing more reopen from Session Restore in Aurora, using 2.4 GB RAM.")

(And seeing, Performance regression: NS 2.6.8.7+ hogs memory on Fx 3.6, http://forums.informaction.com/viewtopi ... 10&t=18986, figured I see if reverting to an earlier NoScript in Aurora had any affect on my RAM usage, & it did not.)


And as it turns out, just yesterday on waking my computer from sleep, I said "so i left SeaMonkey running, put the computer to sleep, now that i'm back SeaMonkey is sitting there like a lump. can't interact with any windows. its not using any CPU or I/O. just sitting there.". (It did not crash, just hung, not to re-awaken.)


Now that's not to say that there isn't some cause/effect, but ...


> Firefox crashes

Crash report numbers (URLs)?

[Pippa]

eab4d692-5e26-4ca5-9b3e-f1cc6d015626

That's the crash report in particular that prompted me to make this post. I wanted to post my entire list, but it's detected by the spam filter. Guess because I'm a guest and not registered.

[barbaz]

I noticed that (SeaMonkey) Aurora memory usage went to hell, so I went looking & the first thing I saw was YEINU: Your Experience Is Not Universal (even though it probably does not apply in my case .)

("Aurora is also using quite a bit more RAM then 2.23. 1.7 GB running 2.23 for a short while, then close down & doing nothing more reopen from Session Restore in Aurora, using 2.4 GB RAM.")

@therube, I'm not noticing this with nightly, you might want to run about:addons-memory to check if the culprit is one your extensions
(it should work fine on aurora even though amo thinks it's incompatible)

[therube]

> eab4d692-5e26-4ca5-9b3e-f1cc6d015626

I wasn't able to get anything with that number?

> about:addons-memory

http://forums.informaction.com/viewtopi ... 18&t=18999

[Plipp]

> eab4d692-5e26-4ca5-9b3e-f1cc6d015626

I wasn't able to get anything with that number?

When I view a report, is it erased from my history? That's really dumb if so. I can't even find part of the number to make sure I copied the entire thing... I had the crash at 1/16/2014 11:54am. (literally less than 5 minutes from the time I posted at 4:58 UTC). If I have my time zones wrong, I'd have had a crash at 12:54pm then. The earliest I have for that day is a 3:40 (and hell, I don't remember it crashing at that time).

[Plipp]

OK. So after you click on a report, your report number is completely changed. Who thought that was a good idea? And I couldn't find it again because the timestamp for it gets changed on the about:crashes page. Brilliant!

https://crash-stats.mozilla.com/report/ ... 5db2140117

So this is the report. I only identified it because it was purple and it happened to have a nice number for the "Time since crash" or whatever.