mozjs.dll crash 26.0.3

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.
Please direct questions that are Mac or Linux-specific (dealing with installation and OS integration) to the appropriate Linux or Mac board.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only. The main focus here is on Pale Moon on Windows. Please direct your questions that are specific for Linux and Mac to the dedicated boards for those operating systems.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
Locked
PhilK

mozjs.dll crash 26.0.3

Post by PhilK » 2016-02-13, 13:49

Had PaleMoon x64 crash yesterday while viewing a wikipedia page and pressing an arrow button. I don't know why an arrow button would precipitate such a thing, unless one of my extensions had something to do with it. (For example, I use "Imagus", which expands image thumbnails or image links on a page when hovering over them.)

Here are the Windows crash details (Windows 7 Ultimate x64):

Problem signature:
Problem Event Name: APPCRASH
Application Name: palemoon.exe
Application Version: 26.0.3.5878
Application Timestamp: 56b3ccbd
Fault Module Name: mozjs.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 56b3bb76
Exception Code: c0000005
Exception Offset: 0000000000086ad0
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: f59f
Additional Information 2: f59f25ce703755d3776f4d5952540efb
Additional Information 3: 1e94
Additional Information 4: 1e945405e700f9d91e2a1e9d902f06a3

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 29249
Joined: 2011-08-28, 17:27
Location: Tranås, SE
Contact:

Re: mozjs.dll crash 26.0.3

Post by Moonchild » 2016-02-13, 13:59

Please use AppCrashView to get a more detailed report about the crash.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss
Image

PhilK

Re: mozjs.dll crash 26.0.3

Post by PhilK » 2016-02-13, 14:11

Here's what AppCrashView shows:
===================================

Version=1
EventType=APPCRASH
EventTime=130997813554523749
ReportType=2
Consent=1
ReportIdentifier=7ce0d8c0-d1c4-11e5-b3d5-0250d53b0901
IntegratorReportIdentifier=7ce0d8bf-d1c4-11e5-b3d5-0250d53b0901
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=palemoon.exe
Sig[1].Name=Application Version
Sig[1].Value=26.0.3.5878
Sig[2].Name=Application Timestamp
Sig[2].Value=56b3ccbd
Sig[3].Name=Fault Module Name
Sig[3].Value=mozjs.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=56b3bb76
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000086ad0
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=f59f
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=f59f25ce703755d3776f4d5952540efb
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1e94
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=1e945405e700f9d91e2a1e9d902f06a3
UI[2]=D:\Apps_64\Inet\PaleMoon\palemoon.exe
UI[3]=Pale Moon web browser has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Apps_64\Inet\PaleMoon\palemoon.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\USER32.dll
LoadedModule[5]=C:\Windows\system32\GDI32.dll
LoadedModule[6]=C:\Windows\system32\LPK.dll
LoadedModule[7]=C:\Windows\system32\USP10.dll
LoadedModule[8]=C:\Windows\system32\msvcrt.dll
LoadedModule[9]=D:\Apps_64\Inet\PaleMoon\MSVCR110.dll
LoadedModule[10]=C:\Windows\system32\IMM32.DLL
LoadedModule[11]=C:\Windows\system32\MSCTF.dll
LoadedModule[12]=D:\Apps_64\Inet\PaleMoon\nss3.dll
LoadedModule[13]=C:\Windows\system32\WINMM.dll
LoadedModule[14]=C:\Windows\system32\WSOCK32.dll
LoadedModule[15]=C:\Windows\system32\WS2_32.dll
LoadedModule[16]=C:\Windows\system32\RPCRT4.dll
LoadedModule[17]=C:\Windows\system32\NSI.dll
LoadedModule[18]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[19]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[20]=D:\Apps_64\Inet\PaleMoon\MSVCP110.dll
LoadedModule[21]=D:\Apps_64\Inet\PaleMoon\mozglue.dll
LoadedModule[22]=D:\Apps_64\Inet\PaleMoon\mozjs.dll
LoadedModule[23]=C:\Windows\system32\PSAPI.DLL
LoadedModule[24]=D:\Apps_64\Inet\PaleMoon\mozalloc.dll
LoadedModule[25]=D:\Apps_64\Inet\PaleMoon\gkmedias.dll
LoadedModule[26]=C:\Windows\system32\ole32.dll
LoadedModule[27]=C:\Windows\system32\MSIMG32.dll
LoadedModule[28]=D:\Apps_64\Inet\PaleMoon\xul.dll
LoadedModule[29]=C:\Windows\system32\NETAPI32.dll
LoadedModule[30]=C:\Windows\system32\netutils.dll
LoadedModule[31]=C:\Windows\system32\srvcli.dll
LoadedModule[32]=C:\Windows\system32\wkscli.dll
LoadedModule[33]=C:\Windows\system32\SAMCLI.DLL
LoadedModule[34]=C:\Windows\system32\SHELL32.dll
LoadedModule[35]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[36]=C:\Windows\system32\VERSION.dll
LoadedModule[37]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[38]=C:\Windows\system32\WINNSI.DLL
LoadedModule[39]=C:\Windows\system32\UxTheme.dll
LoadedModule[40]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[41]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[42]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[43]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[44]=C:\Windows\system32\dwmapi.dll
LoadedModule[45]=C:\Windows\system32\dwrite.dll
LoadedModule[46]=C:\Program Files\NVIDIA Corporation\nview\nview64.dll
LoadedModule[47]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\COMCTL32.dll
LoadedModule[48]=C:\Windows\system32\ntmarta.dll
LoadedModule[49]=C:\Windows\system32\WLDAP32.dll
LoadedModule[50]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[51]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[52]=C:\Windows\system32\propsys.dll
LoadedModule[53]=C:\Windows\system32\mswsock.dll
LoadedModule[54]=C:\Windows\System32\wshtcpip.dll
LoadedModule[55]=D:\Apps_64\Inet\PaleMoon\browser\components\browsercomps.dll
LoadedModule[56]=C:\Windows\system32\WINTRUST.dll
LoadedModule[57]=C:\Windows\system32\CRYPT32.dll
LoadedModule[58]=C:\Windows\system32\MSASN1.dll
LoadedModule[59]=C:\Windows\system32\dxgi.dll
LoadedModule[60]=C:\Windows\system32\d3d10_1.dll
LoadedModule[61]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[62]=C:\Windows\system32\d3d11.dll
LoadedModule[63]=C:\Windows\system32\nvwgf2umx.dll
LoadedModule[64]=C:\Windows\system32\d2d1.dll
LoadedModule[65]=C:\Windows\system32\mscms.dll
LoadedModule[66]=C:\Windows\system32\USERENV.dll
LoadedModule[67]=C:\Windows\system32\profapi.dll
LoadedModule[68]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[69]=C:\Windows\system32\rsaenh.dll
LoadedModule[70]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[71]=C:\Windows\System32\MMDevApi.dll
LoadedModule[72]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[73]=D:\Apps_64\Inet\PaleMoon\softokn3.dll
LoadedModule[74]=D:\Apps_64\Inet\PaleMoon\nssdbm3.dll
LoadedModule[75]=D:\Apps_64\Inet\PaleMoon\freebl3.dll
LoadedModule[76]=D:\Apps_64\Inet\PaleMoon\nssckbi.dll
LoadedModule[77]=C:\Windows\system32\NLAapi.dll
LoadedModule[78]=C:\Windows\system32\napinsp.dll
LoadedModule[79]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[80]=C:\Windows\system32\DNSAPI.dll
LoadedModule[81]=C:\Windows\System32\winrnr.dll
LoadedModule[82]=C:\Program Files\Bonjour\mdnsNSP.dll
LoadedModule[83]=C:\Windows\system32\WININET.dll
LoadedModule[84]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[85]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[86]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[87]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[88]=C:\Windows\system32\normaliz.DLL
LoadedModule[89]=C:\Windows\system32\iertutil.dll
LoadedModule[90]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[91]=C:\Windows\system32\Secur32.dll
LoadedModule[92]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[93]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[94]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[95]=C:\Windows\System32\wship6.dll
LoadedModule[96]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[97]=C:\Windows\system32\nvapi64.dll
LoadedModule[98]=C:\Windows\system32\explorerframe.dll
LoadedModule[99]=C:\Windows\system32\DUser.dll
LoadedModule[100]=C:\Windows\system32\DUI70.dll
LoadedModule[101]=C:\Windows\system32\rasadhlp.dll
LoadedModule[102]=C:\Windows\system32\LINKINFO.dll
LoadedModule[103]=C:\Windows\system32\ntshrui.dll
LoadedModule[104]=C:\Windows\system32\cscapi.dll
LoadedModule[105]=C:\Windows\system32\slc.dll
LoadedModule[106]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[107]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[108]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[109]=C:\Windows\system32\mfplat.dll
LoadedModule[110]=C:\Windows\system32\AVRT.dll
LoadedModule[111]=C:\Windows\system32\mfreadwrite.dll
LoadedModule[112]=C:\Windows\system32\mf.dll
LoadedModule[113]=C:\Windows\system32\ATL.DLL
LoadedModule[114]=C:\Windows\system32\ksuser.dll
LoadedModule[115]=C:\Windows\system32\dxva2.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Pale Moon web browser
AppPath=D:\Apps_64\Inet\PaleMoon\palemoon.exe

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 29249
Joined: 2011-08-28, 17:27
Location: Tranås, SE
Contact:

Re: mozjs.dll crash 26.0.3

Post by Moonchild » 2016-02-13, 14:18

At first glance this looks like a potential compat issue with the loaded NVidia modules. It would need a debugger attached to actually see what's going on, though.

This may actually get solved in 26.1 so please see if that version does any better (will be out next week).
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss
Image

PhilK

Re: mozjs.dll crash 26.0.3

Post by PhilK » 2016-02-13, 14:28

Moonchild wrote:At first glance this looks like a potential compat issue with the loaded NVidia modules. It would need a debugger attached to actually see what's going on, though.

This may actually get solved in 26.1 so please see if that version does any better (will be out next week).

Thanks. Unfortunately this is probably going to be hard to verify because I don't have issues with wikipedia pages in general and PaleMoon (even 26.0.3) hasn't been crashing much, but I will certainly use the new version and report if I see any other crashes.

My biggest worry these days is losing access to all the extensions that I rely upon to add important functionality, given the Goanna fork and the killing-off of non-signed extensions for mainline FF.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 29249
Joined: 2011-08-28, 17:27
Location: Tranås, SE
Contact:

Re: mozjs.dll crash 26.0.3

Post by Moonchild » 2016-02-13, 14:30

PhilK wrote: given the Goanna fork and the killing-off of non-signed extensions for mainline FF.
Goanna is our rendering and layout engine -- this doesn't really have much if anything to do with extension compatibility.
Signed extensions is something we won't enforce.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss
Image

PhilK

Re: mozjs.dll crash 26.0.3

Post by PhilK » 2016-02-13, 14:39

Moonchild wrote:
PhilK wrote: given the Goanna fork and the killing-off of non-signed extensions for mainline FF.
Goanna is our rendering and layout engine -- this doesn't really have much if anything to do with extension compatibility.
Signed extensions is something we won't enforce.

I understand and appreciate your position on signed extensions. (And your stance on most issues, tbh, which is why I usually use PaleMoon as my primary browser these days. ;) )

But I guess wrt to Goanna it's probably more accurate to say "the changes to PM 26+ that change compatibility with, or require special versions of current FF extensions". I'm guessing once FF ESR switches to the v44+ codebase, most extension developers will stop developing for earlier FF versions. (Or, I assume, most forks which forked prior to that point.)

Some extensions I use - eg HackTheWeb installed on a FF ESR installation here - probably will never be updated because they are abandoned so when ESR shifts to the newer codebase, that extension will become useless. (I already have to keep a downrev version of Stylish on that install, because HTW isn't compatible with Stylish 2.x)

User avatar
Pallid Planetoid
Knows the dark side
Knows the dark side
Posts: 3843
Joined: 2015-10-06, 16:59
Location: Los Angeles CA USA

Re: mozjs.dll crash 26.0.3

Post by Pallid Planetoid » 2016-02-13, 17:04

Moonchild wrote: Signed extensions is something we won't enforce.
:clap: One of the many reasons to use Pale Moon :thumbup:
Current Pale Moon(x86) Release | WIN10 | I5 CPU, 1.7 GHz, 6GB RAM, 500GB HD[20GB SSD]
Formerly user Pale Moon Rising - to provide context involving embedded reply threads.
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Knowing Pale Moon is indisputably #1 is defined by knowing the totality of browsers. - Pale Moon Rising

Locked