Recent crashes with Pale Moon

Walker D · Post by **Walker D** » 2013-06-19, 17:50

I'm also having annoying problems with PaleMoon crashing all the time..
I don't need to open too much tabs before it crashes, and I noticed that the main process palemoon.exe gets weirdly high fast ...(it generally crashes getting near 900.000 K ). This behavior started recently, and I don't really know why.
I'm on Palemoon 20.1 32bits, Windows 7 32bits.

EDIT: Here are the data logs that I got from the crashes:

WhatIsHang data:

Walker D · Post by **Walker D** » 2013-06-23, 06:10

(posting the other logs in a different post cause it was over the maximum number of allowed characters already).

AppCrash data:
- palemoon.exe

- plugin-container.exe

Hope someone can give me some help with that :p

Post by **Moonchild** » 2013-06-23, 09:36

That's a really odd hang, at first glance it seems to be caused in the directx back-end.

The plugin-container's "80000003" crash code is one I've seen in case debug libraries for DirectX are used. Did you install the DirectX SDK on your system by any chance, or did you select "debug libraries" in a DirectX control panel applet?

Did you recently update your graphics drivers?

Also, I see you are using Avast - can you please try to make the necessary exceptions for Pale Moon in Avast so it is completely excluded from real-time scanning or behavior scanning, and let me know if that helps?

Tweakzy · Post by **Tweakzy** » 2013-06-30, 16:11

i had a few crashed latley

what i did was turn of hardware acceleration
opened task manager right clicked on palemoons process and set the affinity to 1 core
because i have nvidia i opened the nvidia control pannel then under 3d settings turned off all for palemoon

it fixed the crashes and the flash player problems too.

hope that helps

Walker D · Post by **Walker D** » 2013-08-02, 21:46

Moonchild wrote:That's a really odd hang, at first glance it seems to be caused in the directx back-end.

The plugin-container's "80000003" crash code is one I've seen in case debug libraries for DirectX are used. Did you install the DirectX SDK on your system by any chance, or did you select "debug libraries" in a DirectX control panel applet?

Did you recently update your graphics drivers?

Also, I see you are using Avast - can you please try to make the necessary exceptions for Pale Moon in Avast so it is completely excluded from real-time scanning or behavior scanning, and let me know if that helps?

Hi ..sorry for this late answer ( I was too focused on exams and other RL stuff..)

Well, after my last post, Palemoon released two updates I think ..having them installed now, the scenarios are still the same.

Seems like in other user accounts, Palemoon works weirdly slow (struggling a bit), but it doesn't seems to crash like it do here on my user account (here it runs kinda normally, no much struggle, but then, it crashes ..with the palemoon.exe process getting high fast (as I said previously, crashes when it gets near 900.000 K ..what is happening during a normal use for me).

My graphics card is a ATI Radeon HD 5450, and I don't update its drivers since January.

About the DirectX SDK, I don't know for sure ...my brother uses this PC (another user account) and he installs some games sometimes, generally from Steam. There's some way that I can verify the information that you need related to that?

Looking to my installed programs, I saw a "NVIDIA PhysX" ..probably was automatically installed with some game that my brother installed here.. ..is that a possible problem?

About Avast, I think I always used it ..don't know how it would be causing problems just now.. ..but there's any downside about excluding Palemoon on it the way you asked? (I'm yet to discover how to do it though ..what I saw there at least is that it's firewall and browser integration are disabled.

Any other info that you need to understand my case, feel free to ask.

Post by **satrow** » 2013-08-03, 01:58

PhysX is nVidia only, it really shouldn't load if there's no hardware for it to run on. The HD 5450 is low-end but should work with hardware acceleration as far as I can tell.

The Avast! problems often stem from the new 'sandboxing' that it uses; from the main Avast window > Security tab > Antivirus > File System Shield > Settings. There you'll see the AutoSandbox settings; I enable it but set the Mode to Ask, not to AutoSandbox.

When Avast! AutoSandboxes, as in the default setting, it does so without any warning, this can lead to all kinds of weird behaviour in the software that it affects. You may also need to exclude the Pale Moon executable file, as well as any Plugin containers, from Avast. I've set it up this way and have had zero issues since doing so.

Walker D · Post by **Walker D** » 2013-08-03, 22:59

satrow wrote:PhysX is nVidia only, it really shouldn't load if there's no hardware for it to run on. The HD 5450 is low-end but should work with hardware acceleration as far as I can tell.

The Avast! problems often stem from the new 'sandboxing' that it uses; from the main Avast window > Security tab > Antivirus > File System Shield > Settings. There you'll see the AutoSandbox settings; I enable it but set the Mode to Ask, not to AutoSandbox.

Ok, I uninstalled the PhysX software, just in case.. ..about the hardware acceleration on Palemoon, it's a option on 32bits systems? ..if so, how I enable it?
Changed the AutoSandbox from Auto to Ask.

satrow wrote:You may also need to exclude the Pale Moon executable file, as well as any Plugin containers, from Avast.

About this exclusion, do you mean adding to the AutoSandbox's exclusion list? Cause I didn't find a list on Avast where I could delete Palemoon
from..

On File System Shield settings, on the Exclusions tab, there's " *\firefox\profiles\*sessionstore*.js " with the W selected (write) ..should I select the other letters and add some Palemoon specific entries (or even add directly to global exclusions)?

Post by **Moonchild** » 2013-08-03, 23:25

An FYI: the PhysX runtime may be used by games - it's not something that is NVidia exclusive although it's released by NVidia - ATI cards can also be used by the PhysX runtime.

The "breakpoint" error, however, would be something else, I gather, if the AV sandboxing setting does nothing to relieve the issue. In that case, you should see if you have a "directx control panel applet" in your control panel, and if so, check to make sure the libraries selected in it are "release" libraries and not "debug" ones. The debug libraries are known to cause these issues.

A potential fix would be to install the SDK: http://www.microsoft.com/en-us/download ... px?id=6812 and use the control panel applet included with it to make sure to use the release libs. I think some games might install different versions of DirectX which could be the cause if those games use debug versions.

Walker D · Post by **Walker D** » 2013-08-04, 03:30

Moonchild wrote:An FYI: the PhysX runtime may be used by games - it's not something that is NVidia exclusive although it's released by NVidia - ATI cards can also be used by the PhysX runtime.

The "breakpoint" error, however, would be something else, I gather, if the AV sandboxing setting does nothing to relieve the issue. In that case, you should see if you have a "directx control panel applet" in your control panel, and if so, check to make sure the libraries selected in it are "release" libraries and not "debug" ones. The debug libraries are known to cause these issues.

A potential fix would be to install the SDK: http://www.microsoft.com/en-us/download ... px?id=6812 and use the control panel applet included with it to make sure to use the release libs. I think some games might install different versions of DirectX which could be the cause if those games use debug versions.

damn ..ok, I reinstalled the PhysX thing ..hope games can still access it :p

Well, I didn't find any directx control panel applet (you mean like a tab?) and didn't find any directx's process running.. ..also, couldn't find the configuration of the DirectX installed here.. ..so, needing some info about my DirectX configurations, please tell me where I can find it, if necessary.

I will reboot the system and do some tests now (I didn't install the SDK that you linked at this point though) ...If I see any improvements after this test, I'll report it back tomorrow..

Post by **Moonchild** » 2013-08-04, 06:51

re: DirectX SDK

You have to understand that some games may install DirectX libraries, and some games don't ship the correct libraries. By default, you don't see anything of DirectX as it is just that: a set of libraries from windows programs to use. The control panel applet (which you would find as in icon in control panel when not using the "category view") is installed as part of the SDK which gives you control over which libraries are used. A default DirectX runtime installation will not install this control panel applet (dxcpl.cpl) so you won't have it in that case. Is that clearer?

In any case, it's something i've been able to discern by doing some research myself, it's not a sure-fire way to solve the breakpoint crash, but it seems some people at least have had success with it; since it's such an odd error to get, any hints is better than none.

Pale Moon forum

Recent crashes with Pale Moon

Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon

Re: Recent crashes with Pale Moon