Has your browser ever crashed after a long session? This just happened to me.

[inf1nity]

I am palemoon user. I haven't kept it updated for sometime now(i'm on 24.5) I had been using it to browse the internet for the past 2 hours continuously without a break. I had been visiting all sorts of script-heavy and image-heavy sites, reddit, imgur, various sites from reddit links, facebook, tumblr

After two hours of browsing, it suddenly disappeared. No error, no "Not Responding" message, no "Has stopped Working" message, it just dissappeared. Oh well.

I disconnected my internet and ran CCLeaner to scrub away the accumulated grime. Started it up again. Running smoothly now.


Looks like i'm gonna have to plug in a spare USB drive for readyboost once again lol. 😎

 

[Dude111]

Yes Im running MyIE2 and its happend to me also!!!!!!

Sometimes I get lucky and I can create a TAB GROUP and save the remaining tabs I have open but not always........ (Sometimes I cant do anything but close the browser when it happens))

I guess browsers like this that have TABS can be very heavy on usage...... (My 'MAX tabs' is set to 100 right now)

 

[Morbus]

This is normal in any software, to be honest. If you use something very often, or for a very long period of time, you're bound to find issues like these sooner or later.

I have personally never found a single piece of software that I've used a lot hasn't crashed. It's just, fortunately or not, the nature of software.

 

[sandorski]

I leave FF open for weeks at a time, often with a dozen or more tabs open the whole time. Everyday I open/close probably 100ish tabs as well. Usually what forces me to restart FF is a Windows Update or Flash begins crashing due to an Update needing to be installed.

If your browser is crashing just after a few hours I suspect it has stability issues. Although, there might be a Hardware stability issue involved.

 

[code65536]

Is this 32- or 64-bit Pale Moon? Did you run out of memory? OOM crashes (in general, not just in Firefox) are often silent (esp. if it's 32-bit and the OOM also involves exhausted address space). That's because the code to handle the exception or display the error can't run because, well, it's out of memory.

("Not responding" just means that the program's message pump isn't responding to messages from the OS, which usually means that the program has hanged--often, run into a loop it couldn't get out of. Errors that kill the program outright doesn't trigger "not responding" errors. "Has stopped working" is an unhandled exception and is usually what you'd see if there's an OOM problem, though, again, many OOM die quietly--it depends on how exactly the OOM was triggered.)

 

[Cerb]

2 hours? No. But, FF crashes on me every 1-2 days, typically. No not responding, just dies, brings up the crash reported, and I tell it to restart (or I come back to the crash reported after being away from the PC).

 

[VirtualLarry]

2 hours? No. But, FF crashes on me every 1-2 days, typically. No not responding, just dies, brings up the crash reported, and I tell it to restart (or I come back to the crash reported after being away from the PC).

I had that on my HTPC (G1610, 8GB DDR3, HDMI output, ECS H61 ITX mobo, Win7 64-bit), with Waterfox 29.0. Problem seems to have disappeared with Waterfox 30.0.

 

[inf1nity]

I leave FF open for weeks at a time, often with a dozen or more tabs open the whole time. Everyday I open/close probably 100ish tabs as well. Usually what forces me to restart FF is a Windows Update or Flash begins crashing due to an Update needing to be installed.

If your browser is crashing just after a few hours I suspect it has stability issues. Although, there might be a Hardware stability issue involved.

yup my PC is old and sucks ass.

Open for weeks at a time?? What do you do with that?

 

[inf1nity]

Is this 32- or 64-bit Pale Moon? Did you run out of memory? OOM crashes (in general, not just in Firefox) are often silent (esp. if it's 32-bit and the OOM also involves exhausted address space). That's because the code to handle the exception or display the error can't run because, well, it's out of memory.

("Not responding" just means that the program's message pump isn't responding to messages from the OS, which usually means that the program has hanged--often, run into a loop it couldn't get out of. Errors that kill the program outright doesn't trigger "not responding" errors. "Has stopped working" is an unhandled exception and is usually what you'd see if there's an OOM problem, though, again, many OOM die quietly--it depends on how exactly the OOM was triggered.)

Thanks for the info. Its 32 bit running on 32 bit Windows 7. I guess i probably ran out of memory since i'm low on RAM.

 

[sandorski]

yup my PC is old and sucks ass.

Open for weeks at a time?? What do you do with that?

Leave it running.

 

[Cerb]

I had that on my HTPC (G1610, 8GB DDR3, HDMI output, ECS H61 ITX mobo, Win7 64-bit), with Waterfox 29.0. Problem seems to have disappeared with Waterfox 30.0.

I'm using plain old FF. I should move to a 64-bit one, but tend to leave that for Linux.

 

[VirtualLarry]

I'm using plain old FF. I should move to a 64-bit one, but tend to leave that for Linux.

Waterfox! I've been using it for months, if not years. Works great, generally.

However, some plugins, like the DivX player, are 32-bit only, and require you to use Firefox if you use those plugins (for watching movies online, etc).

 

[Muse]

I leave FF open for weeks at a time, often with a dozen or more tabs open the whole time. Everyday I open/close probably 100ish tabs as well. Usually what forces me to restart FF is a Windows Update or Flash begins crashing due to an Update needing to be installed.

If your browser is crashing just after a few hours I suspect it has stability issues. Although, there might be a Hardware stability issue involved.

Pale Moon crashed twice on me today already on this Win7 32bit laptop, just happened 5 minutes ago. Have 6 windows with 58 tabs. Have been getting crashes almost daily for a week or two. I've been wondering if it's a Pale Moon thing or if I'd have the same problems using Firefox. I've gotten messages that Pale Moon has stopped working with an OK button. 😕

 

[code65536]

Pale Moon crashed twice on me today already on this Win7 32bit laptop, just happened 5 minutes ago. Have 6 windows with 58 tabs. Have been getting crashes almost daily for a week or two. I've been wondering if it's a Pale Moon thing or if I'd have the same problems using Firefox. I've gotten messages that Pale Moon has stopped working with an OK button. 😕

What does the memory usage look like in Process Explorer (or Task Manager)?

My guess is that it's pretty high.

If you have that many tabs open, you really need a 64-bit OS with a 64-bit browser backed by extra RAM. The thing is, the web has become increasingly fat and heavy these days (it's not that web browsers are less efficient--it's that the nature of content has changed in recent years).

If that is not an option, then I would strongly recommend installing NoScript. (also post #14 in that thread)

(I've had Chrome, which is a lot more memory-hungry than Firefox, gobble up 4GB with just 13 tabs open.)

 

[Muse]

Before the last crash I had last night (the 3rd of the day IIRC), Pale Moon was extremely sluggish, I'd elected to restore all the windows and tabs from the previous launch (i.e. around 60 tabs), and vertical scrolling of pages was extremely slow, laggy, latent... Then the crash came not long after as I was intently reading a page. Argh. So, I reopened the browser and elected not to restore and things were better. Didn't have a chance to check out the memory usage, didn't see this post until now. The machine has 32 bit because I have several apps that behave better (or at all) only on 32 bit Windows. I'll try to limit my open windows/tabs more, close stuff I don't need, and maybe try that no-script thing you suggest. Thanks!

 

[inf1nity]

Pale Moon crashed twice on me today already on this Win7 32bit laptop, just happened 5 minutes ago. Have 6 windows with 58 tabs. Have been getting crashes almost daily for a week or two. I've been wondering if it's a Pale Moon thing or if I'd have the same problems using Firefox. I've gotten messages that Pale Moon has stopped working with an OK button. 😕

Did you get a BEX error? Palemoon and chrome both have been crashing for me today for no reason apparantly. Palemoon crash gives me a BEX error whereas chrome crashes without any message. I had just 6-7 tabs open at the time it crashed.

Problem signature:
Problem Event Name: BEX
Application Name: palemoon.exe
Application Version: 24.5.0.5222
Application Timestamp: 53529afd
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 1893a9d0
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 

[code65536]

Did you get a BEX error? Palemoon and chrome both have been crashing for me today for no reason apparantly. Palemoon crash gives me a BEX error whereas chrome crashes without any message. I had just 6-7 tabs open at the time it crashed.

Does PaleMoon have a crash reporter like Firefox? In Firefox, you can go to about:crashes and see a list of recent crashes and the crash reports for each. That's a lot more useful than the generic Windows crash dialog because it has a better understanding of things--e.g., it will contain symbols.

Anyway, a StackHash crash just means that it crashed at an instruction that wasn't in a loaded executable. For web browsers, what this usually means is that it crashed on dynamically-generated code--i.e., a piece of JavaScript. (vs. crashing on a piece of pre-compiled code, like say the layout engine, compositor, or other parts of Firefox's core Gecko engine). StackHash crashes could be the result of a bug in the JavaScript engine (since bad JavaScript should fail without taking the browser down), or, perhaps more likely, the result of an out-of-memory error. What was the process's memory usage like at the moment of the crash?

 

[Maximilian]

Not since I stopped using firefox :biggrin:

Its why I ditched it at firefox 4.0, it would crash but luckily it remembered the tabs I had open most of the time. Kinda got fed up with it.

 

[Muse]

Did you get a BEX error? Palemoon and chrome both have been crashing for me today for no reason apparantly. Palemoon crash gives me a BEX error whereas chrome crashes without any message. I had just 6-7 tabs open at the time it crashed.

I didn't see anything mentioning BEX. Just saw a little window saying PM had stopped working, if I get another I'll post the exact message here. Right now I'm trying not to get too many tabs open.

I did have a nervous episode around an hour ago. Not a whole lot open, maybe 20-30 tabs max in two windows. But Pale Moon kind of locked up for a minute or so with a spinning circle for a cursor (equivalent to the hour glass). It resolved, though.

 

[inf1nity]

Does PaleMoon have a crash reporter like Firefox? In Firefox, you can go to about:crashes and see a list of recent crashes and the crash reports for each. That's a lot more useful than the generic Windows crash dialog because it has a better understanding of things--e.g., it will contain symbols.

PM doesn't have a crash reporter AFAIK. The about:crashes thing is useless for me since it doesn't work in PM and even if it did, it would be useless since i uninstalled PM and installed a newer version in its place.

Anyway, a StackHash crash just means that it crashed at an instruction that wasn't in a loaded executable. For web browsers, what this usually means is that it crashed on dynamically-generated code--i.e., a piece of JavaScript. (vs. crashing on a piece of pre-compiled code, like say the layout engine, compositor, or other parts of Firefox's core Gecko engine). StackHash crashes could be the result of a bug in the JavaScript engine (since bad JavaScript should fail without taking the browser down), or, perhaps more likely, the result of an out-of-memory error. What was the process's memory usage like at the moment of the crash?

I don't visit a lot of new websites everyday. My regular websites include reddit, 4chan's /g/ board, this forum and a couple of others. I don't see why websites that run okay normally would cause crash yesterday.

As far as memory usage, i didn't monitor it, but i don't think there would have been a memory issue, since even though i have low RAM, only 6-7 tabs were open, all contained fairly light webpages.


Thanks for telling me about StackHash. Learned something new today thanks to you :thumbsup:

 

[inf1nity]

I didn't see anything mentioning BEX. Just saw a little window saying PM had stopped working, if I get another I'll post the exact message here. Right now I'm trying not to get too many tabs open.

I did have a nervous episode around an hour ago. Not a whole lot open, maybe 20-30 tabs max in two windows. But Pale Moon kind of locked up for a minute or so with a spinning circle for a cursor (equivalent to the hour glass). It resolved, though.

Don't you look at the details of the error message after the crash?

As for the second part, that happens with me too. Palemoon often locks up and turns into a "Not Responding" program for about 10 seconds when lots of tabs are open or it has to render a page with complicated coding.

 

[inf1nity]

If that is not an option, then I would strongly recommend installing NoScript. (also post #14 in that thread)

(I've had Chrome, which is a lot more memory-hungry than Firefox, gobble up 4GB with just 13 tabs open.)

I also back this suggestion(awesome post btw). I also recommend installing FlashBlock so that flash objects don't initialize automatically, saving some more memory.

 

[Muse]

Don't you look at the details of the error message after the crash?

I sometimes do, although I'm usually mystified as to what they mean. But in the PM crashes I've had so many of the last week or so I don't recall seeing a button in the message that showed details. Are they available elsewhere?