Page 1 of 1
Pale Moon Crash - Maybe Avast?
Posted: 2018-12-31, 23:24
by illiad
Are there any issues with Avast??
Problem signature:
Problem Event Name: APPCRASH
Application Name: palemoon.exe
Application Version: 4.1.7.6912
Application Timestamp: 5c06e628
Fault Module Name: xul.dll
Fault Module Version: 4.1.7.6912
Fault Module Timestamp: 5c06e8ea
Exception Code: c0000005
Exception Offset: 000000000210cb27
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 43bb
Additional Information 2: 43bb31ccdd0765185f0a34b03bcb7cf7
Additional Information 3: 768c
Additional Information 4: 768c61c84e89e585a6bcdaacedf474cb
Re: Palemoon Crashes After Upgraded to v28.x
Posted: 2019-01-01, 00:05
by Moonchild
The crash address seems to be in the VP8 decoder. I doubt it has anything to do with avast. Further investigation would require an actual crash dump.
Re: Palemoon Crashes After Upgraded to v28.x
Posted: 2019-01-01, 00:16
by Night Wing
On all of my four, 64 bit Windows 7 hard drives, they have free Avast installed on them. I use 32 bit windows Pale Moon 28.2.2 on all of these hard drives and have no problems what so ever with Pale Moon.
Re: Palemoon Crashes After Upgraded to v28.x
Posted: 2019-01-01, 00:20
by illiad
Thanks, managed to get appcrash going, would have gone to bed, but there are a lot of noisy people here in uk!!!!
Do note that folder location is to enable easy upgrade in active directory environment at work
Re: Palemoon Crashes After Upgraded to v28.x
Posted: 2019-01-01, 00:31
by illiad
Night Wing wrote:On all of my four, 64 bit Windows 7 hard drives, they have free Avast installed on them. I use 32 bit windows Pale Moon 28.2.2 on all of these hard drives and have no problems what so ever with Pale Moon.
it may be helpful to try the 64 bit pale moon..
Note that this crash takes quite a few hours to happen on my system, the last crash was 24 hours ago, after which i fully cleared PM, did ccleaner etc, and clean install new PM...
Re: Palemoon Crashes After Upgraded to v28.x
Posted: 2019-01-02, 00:58
by therube
Well it does look like Avast does inject itself into the process space, so see if you can disable that portion?
Code: Select all
LoadedModule[2]=C:\Program Files\AVAST Software\Avast\x64\aswhooka.dll
Re: Pale Moon Crash - Maybe Avast?
Posted: 2019-01-02, 08:39
by Moonchild
Off-topic:Split the topic off -- @illiad, I asked in
viewtopic.php?t=20716#p156758 to not tack your "maybe avast related" issue to Comodo IS threads but you still did anyway. Please save the moderation staff on the forum some work and try to keep separate issues in separate topics? Thanks in advance.
Re: Pale Moon Crash - Maybe Avast?
Posted: 2019-01-03, 10:17
by illiad
sorry, but it is difficult enough to track comments, while preventing a comment from becoming a giant long mess....
my memory fails me, but the right topic was locked I think..
Re: Pale Moon Crash - Maybe Avast?
Posted: 2019-01-03, 10:57
by Moonchild
Off-topic:
Both threads were about Comodo and a startup crash. I asked in one to keep things separate since your crash is not involving Comodo and not a startup crash, and you tacked it onto another about the same issue, instead, while it should be its own topic. I've split things off and that's why we are here now.
If you want this crash to be investigated further, I'll need an actual crash minidump. Please see the howto board on this forum for instructions.