FYI: Basilisk crash

Board for discussions around the Basilisk web browser.

Moderator: Basilisk-Dev

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

FYI: Basilisk crash

Unread post by Pallid Planetoid » 2017-11-25, 05:49

FYI -- because I cannot provide any more information other than to say Basilisk crashed while entering a message (email) on the PayPal web "email" interface as illustrated in the screen-shot:
Basilisk crashes in middle of entering a message to Pay Pal.png
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

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

Re: FYI: Basilisk crash

Unread post by Pallid Planetoid » 2017-11-25, 05:59

It JUST occurred to me that I can provide the Windows Event Viewer info (FWIW):

GENERAL ERROR INFORMATION:
Fault bucket 3037096320, type 476195782
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: basilisk.exe
P2: 4.0.0.6525
P3: 5a0849a9
P4: xul.dll
P5: 4.0.0.6525
P6: 5a084be3
P7: 80000003
P8: 0204da91
P9:
P10:

Attached files:
C:\Users\user\AppData\Local\Temp\WERB716.tmp.WERInternalMetadata.xml
C:\Users\user\AppData\Local\Temp\WERCC6C.tmp.appcompat.txt
C:\Users\user\AppData\Local\Temp\WERD948.tmp.mdmp

These files may be available here:
C:\Users\user\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_basilisk.exe_bb68957ccae285651471e48aaa89e74d9f21ef92_0f631b74

Analysis symbol:
Rechecking for solution: 0
Report Id: 36ebe0af-d1a2-11e7-a126-e02a82d72c10
Report Status: 9
APPLICATION ERROR:
Faulting application name: basilisk.exe, version: 4.0.0.6525, time stamp: 0x5a0849a9
Faulting module name: xul.dll, version: 4.0.0.6525, time stamp: 0x5a084be3
Exception code: 0x80000003
Fault offset: 0x0204da91
Faulting process id: 0x2354
Faulting application start time: 0x01d365adc1b087fa
Faulting application path: C:\Program Files (x86)\Basilisk\basilisk.exe
Faulting module path: C:\Program Files (x86)\Basilisk\xul.dll
Report Id: 36ebe0af-d1a2-11e7-a126-e02a82d72c10
Last edited by Pallid Planetoid on 2017-11-25, 07:31, edited 1 time in total.
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

User avatar
Nigaikaze
Board Warrior
Board Warrior
Posts: 1322
Joined: 2014-02-02, 22:15
Location: Chicagoland

Re: FYI: Basilisk crash

Unread post by Nigaikaze » 2017-11-25, 06:07

Since it was an application crash, it might also help to post info from AppCrashView.
Nichi nichi kore ko jitsu = Every day is a good day.

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

Re: FYI: Basilisk crash

Unread post by Pallid Planetoid » 2017-11-25, 07:26

Nigaikaze wrote:Since it was an application crash, it might also help to post info from AppCrashView.
AppCrashView:
Version=1
EventType=APPCRASH
EventTime=131560616321965754
ReportType=2
Consent=1
UploadTime=131560616348127250
ReportIdentifier=36ebe0b0-d1a2-11e7-a126-e02a82d72c10
IntegratorReportIdentifier=36ebe0af-d1a2-11e7-a126-e02a82d72c10
WOW64=1
Response.BucketId=3037096320
Response.BucketTable=476195782
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=basilisk.exe
Sig[1].Name=Application Version
Sig[1].Value=4.0.0.6525
Sig[2].Name=Application Timestamp
Sig[2].Value=5a0849a9
Sig[3].Name=Fault Module Name
Sig[3].Value=xul.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=4.0.0.6525
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5a084be3
Sig[6].Name=Exception Code
Sig[6].Value=80000003
Sig[7].Name=Exception Offset
Sig[7].Value=0204da91
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Basilisk\basilisk.exe
UI[3]=Basilisk 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]=C:\Program Files (x86)\Basilisk\basilisk.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\Basilisk\mozglue.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\system32\dbghelp.dll
LoadedModule[12]=C:\Windows\system32\VERSION.dll
LoadedModule[13]=C:\Program Files (x86)\Basilisk\MSVCP140.dll
LoadedModule[14]=C:\Program Files (x86)\Basilisk\VCRUNTIME140.dll
LoadedModule[15]=C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
LoadedModule[16]=C:\Windows\system32\ucrtbase.DLL
LoadedModule[17]=C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
LoadedModule[18]=C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
LoadedModule[19]=C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
LoadedModule[20]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
LoadedModule[21]=C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
LoadedModule[22]=C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
LoadedModule[23]=C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
LoadedModule[24]=C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll
LoadedModule[25]=C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll
LoadedModule[26]=C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll
LoadedModule[27]=C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
LoadedModule[28]=C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll
LoadedModule[29]=C:\Windows\system32\api-ms-win-crt-multibyte-l1-1-0.dll
LoadedModule[30]=C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
LoadedModule[31]=C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll
LoadedModule[32]=C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll
LoadedModule[33]=C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll
LoadedModule[34]=C:\Program Files (x86)\Basilisk\nss3.dll
LoadedModule[35]=C:\Windows\system32\WINMM.dll
LoadedModule[36]=C:\Windows\syswow64\USER32.dll
LoadedModule[37]=C:\Windows\syswow64\GDI32.dll
LoadedModule[38]=C:\Windows\syswow64\LPK.dll
LoadedModule[39]=C:\Windows\syswow64\USP10.dll
LoadedModule[40]=C:\Windows\system32\WSOCK32.dll
LoadedModule[41]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[42]=C:\Windows\syswow64\NSI.dll
LoadedModule[43]=C:\Windows\system32\IMM32.DLL
LoadedModule[44]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[45]=C:\Program Files (x86)\Basilisk\lgpllibs.dll
LoadedModule[46]=C:\Program Files (x86)\Basilisk\xul.dll
LoadedModule[47]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[48]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[49]=C:\Windows\syswow64\ole32.dll
LoadedModule[50]=C:\Windows\system32\MSIMG32.dll
LoadedModule[51]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[52]=C:\Windows\system32\WINNSI.DLL
LoadedModule[53]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[54]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[55]=C:\Windows\system32\UxTheme.dll
LoadedModule[56]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[57]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[58]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[59]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[60]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[61]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[62]=C:\Windows\system32\pdh.dll
LoadedModule[63]=C:\Windows\syswow64\USERENV.dll
LoadedModule[64]=C:\Windows\syswow64\profapi.dll
LoadedModule[65]=C:\Windows\system32\dwmapi.dll
LoadedModule[66]=C:\Windows\system32\ntmarta.dll
LoadedModule[67]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[68]=C:\Windows\system32\dwrite.dll
LoadedModule[69]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\comctl32.dll
LoadedModule[70]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[71]=C:\Windows\system32\propsys.dll
LoadedModule[72]=C:\Windows\system32\Dnsapi.dll
LoadedModule[73]=C:\Windows\system32\mswsock.dll
LoadedModule[74]=C:\Windows\System32\wshtcpip.dll
LoadedModule[75]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[76]=C:\Windows\system32\NLAapi.dll
LoadedModule[77]=C:\Windows\system32\napinsp.dll
LoadedModule[78]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[79]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[80]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[81]=C:\Windows\System32\winrnr.dll
LoadedModule[82]=C:\Windows\system32\wshbth.dll
LoadedModule[83]=C:\Program Files (x86)\Basilisk\softokn3.dll
LoadedModule[84]=C:\Program Files (x86)\Basilisk\nssdbm3.dll
LoadedModule[85]=C:\Program Files (x86)\Basilisk\freebl3.dll
LoadedModule[86]=C:\Program Files (x86)\Basilisk\nssckbi.dll
LoadedModule[87]=C:\Windows\system32\d3d11.dll
LoadedModule[88]=C:\Windows\system32\dxgi.dll
LoadedModule[89]=C:\Windows\system32\igd10umd32.dll
LoadedModule[90]=C:\Windows\system32\d2d1.dll
LoadedModule[91]=C:\Windows\system32\XmlLite.dll
LoadedModule[92]=C:\Windows\system32\mscms.dll
LoadedModule[93]=C:\Windows\system32\WINSTA.dll
LoadedModule[94]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[95]=C:\Windows\system32\rsaenh.dll
LoadedModule[96]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[97]=C:\Windows\System32\MMDevApi.dll
LoadedModule[98]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[99]=C:\Program Files\WIDCOMM\Bluetooth Software\SysWOW64\BtMmHook.dll
LoadedModule[100]=C:\Windows\syswow64\WININET.dll
LoadedModule[101]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[102]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[103]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[104]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[105]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[106]=C:\Windows\syswow64\iertutil.dll
LoadedModule[107]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[108]=C:\Windows\system32\Secur32.dll
LoadedModule[109]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[110]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[111]=C:\Windows\System32\wship6.dll
LoadedModule[112]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[113]=C:\Windows\system32\rasadhlp.dll
LoadedModule[114]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[115]=C:\Windows\system32\explorerframe.dll
LoadedModule[116]=C:\Windows\system32\DUser.dll
LoadedModule[117]=C:\Windows\system32\DUI70.dll
LoadedModule[118]=C:\Windows\system32\apphelp.dll
LoadedModule[119]=C:\Program Files (x86)\Basilisk\mozavutil.dll
LoadedModule[120]=C:\Program Files (x86)\Basilisk\mozavcodec.dll
LoadedModule[121]=C:\Windows\system32\mfplat.dll
LoadedModule[122]=C:\Windows\system32\AVRT.dll
LoadedModule[123]=C:\Windows\system32\mf.dll
LoadedModule[124]=C:\Windows\system32\ATL.DLL
LoadedModule[125]=C:\Windows\system32\ksuser.dll
LoadedModule[126]=C:\Windows\system32\dxva2.dll
LoadedModule[127]=C:\Windows\system32\evr.dll
LoadedModule[128]=C:\Windows\system32\POWRPROF.dll
LoadedModule[129]=C:\Windows\SysWOW64\msmpeg2adec.dll
LoadedModule[130]=C:\Windows\SysWOW64\slc.dll
LoadedModule[131]=C:\Windows\SysWOW64\msmpeg2vdec.dll
LoadedModule[132]=C:\Windows\SysWOW64\bcrypt.dll
LoadedModule[133]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23508_none_5c028c09a01213b0\gdiplus.dll
LoadedModule[135]=C:\Windows\SysWOW64\wer.dll
LoadedModule[136]=C:\Windows\System32\shdocvw.dll
LoadedModule[137]=C:\Windows\system32\LINKINFO.dll
LoadedModule[138]=C:\Windows\system32\ntshrui.dll
LoadedModule[139]=C:\Windows\system32\srvcli.dll
LoadedModule[140]=C:\Windows\system32\cscapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=iData=1/nDumpFile=//Upload//iCab//139-7dcb33e4fdf14e95b2c2c2f678cc1984-ca19045f30a7b0fecc622bc6b5066980-1-2045245313220241792-AppCrash32-6-1-7601-2.cab/nDumpServer=watson.microsoft.com/nResponseServer=watson.microsoft.com/nResponseURL=//dw//StageFour.asp?iBucket=2045245313220241792&szCab=7dcb33e4fdf14e95b2c2c2f678cc1984.cab&EventType=AppCrash32&BucketHash=ca19045f30a7b0fecc622bc6b5066980&MID=F828E269-6AA7-487B-AB2F-FED75CBD4C3F/nBucket=-1257870976/nBucketTable=476195782/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Basilisk
AppPath=C:\Program Files (x86)\Basilisk\basilisk.exe
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

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35473
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: FYI: Basilisk crash

Unread post by Moonchild » 2017-11-25, 09:12

It was a deliberate crash triggered by our code; the only way to troubleshoot those kinds of crashes is with a crashdump, unfortunately (since I'd need to see the stack trace of it).
Since I'm assuming you can't reproduce this easily, this may be problematic to pinpoint. Sorry that you lost your typed e-mail contents in a crash.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked