Basilisk crashing daily Topic is solved

Forum for discussions around the Basilisk web browser.

Moderator: satrow

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Basilisk crashing daily

Postby Hitchhiker » Wed, 10 Jan 2018, 12:03

Basilisk appears to be crashing every day just recently even though it's only being used for browsing. I've attached a few reports as generated by Windows 8.1 Reliability Monitor.

The system is fully up to date and the latest GPU drivers have been installed (Nvidia 390.65).

Code: Select all

Faulting application name: basilisk.exe, version: 4.0.2.6571, time stamp: 0x5a44b85a
Faulting module name: xul.dll, version: 4.0.2.6571, time stamp: 0x5a44bb62
Exception code: 0x80000003
Fault offset: 0x00000000021b024d
Faulting process id: 0x11d0
Faulting application start time: 0x01d3827d1e61f914
Faulting application path: C:\Program Files\Basilisk\basilisk.exe
Faulting module path: C:\Program Files\Basilisk\xul.dll
Report Id: 89b9ac5c-ee81-11e7-bfe5-0c54a51289ad
Faulting package full name:
Faulting package-relative application ID:


Code: Select all

Description
Faulting Application Path:   C:\Program Files\Basilisk\basilisk.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   basilisk.exe
Application Version:   4.0.2.6579
Application Timestamp:   5a4edfe7
Fault Module Name:   xul.dll
Fault Module Version:   4.0.2.6579
Fault Module Timestamp:   5a4ee6bb
Exception Code:   80000003
Exception Offset:   00000000021af9ad
OS Version:   6.3.9600.2.0.0.768.101
Locale ID:   1033
Additional Information 1:   a9ef
Additional Information 2:   a9eff186869426676f98145a36f1a188
Additional Information 3:   b9c3
Additional Information 4:   b9c3869682816973c9a0b73aa7075f98


Code: Select all

Description
Faulting Application Path:   C:\Program Files\Basilisk\basilisk.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   basilisk.exe
Application Version:   4.0.2.6579
Application Timestamp:   5a4edfe7
Fault Module Name:   xul.dll
Fault Module Version:   4.0.2.6579
Fault Module Timestamp:   5a4ee6bb
Exception Code:   80000003
Exception Offset:   00000000021af9ad
OS Version:   6.3.9600.2.0.0.768.101
Locale ID:   1033
Additional Information 1:   a9ef
Additional Information 2:   a9eff186869426676f98145a36f1a188
Additional Information 3:   b9c3
Additional Information 4:   b9c3869682816973c9a0b73aa7075f98


Code: Select all

Status
Report sent

Description
Faulting Application Path:   C:\Program Files\Basilisk\basilisk.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   basilisk.exe
Application Version:   4.0.2.6579
Application Timestamp:   5a4edfe7
Fault Module Name:   xul.dll
Fault Module Version:   4.0.2.6579
Fault Module Timestamp:   5a4ee6bb
Exception Code:   80000003
Exception Offset:   00000000021af9ad
OS Version:   6.3.9600.2.0.0.768.101
Locale ID:   1033
Additional Information 1:   a9ef
Additional Information 2:   a9eff186869426676f98145a36f1a188
Additional Information 3:   b9c3
Additional Information 4:   b9c3869682816973c9a0b73aa7075f98

Extra information about the problem
Bucket ID:   bbc7bb569daec06aa9c1ebc704db4b3d (1856023761465854781)

I trust the data makes sense to someone.

User avatar
New Tobin Paradigm
Banned user
Banned user
Posts: 4417
Joined: Tue, 09 Oct 2012, 19:37

Re: Basilisk crashing daily

Postby New Tobin Paradigm » Wed, 10 Jan 2018, 12:36

0x80000003 is a hardcoded breakpoint. Our codebases don't have hardcoded breakpoints.. It would help if you gave us the loaded modules from one of your crashes.. Or more properly, a full crash report.. Because it is one of those that is causing this not our code.
Last edited by New Tobin Paradigm on Wed, 10 Jan 2018, 12:36, edited 1 time in total.
I hate Pod Six. Tch, I don't even know why we have a Pod Six. Total suck Pod.
[ ニュー・トビン・パラダイム ]

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Re: Basilisk crashing daily

Postby Hitchhiker » Wed, 10 Jan 2018, 14:04

New Tobin Paradigm wrote:0x80000003 is a hardcoded breakpoint. Our codebases don't have hardcoded breakpoints.. It would help if you gave us the loaded modules from one of your crashes.. Or more properly, a full crash report.. Because it is one of those that is causing this not our code.

Where are the crash reports held in Basilisk? I tried typing about:crashes in the location bar since that works in Firefox, but it appears to be invalid in Basilisk. Likewise, there's no crash data anywhere in about:support. I had a look in my profile, but I'm not sure what I should be looking for in there.

Also, does Basilisk require a particular version of NET Framework to be installed? If so, which one.

User avatar
Nigaikaze
Astronaut
Astronaut
Posts: 692
Joined: Sun, 02 Feb 2014, 22:15
Location: Chicago, IL, USA

Re: Basilisk crashing daily

Postby Nigaikaze » Wed, 10 Jan 2018, 14:07

You can use AppCrashView to post further details about crashes. There's a link to that program here:

viewtopic.php?f=3&t=49

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Re: Basilisk crashing daily

Postby Hitchhiker » Wed, 10 Jan 2018, 15:10

Nigaikaze wrote:You can use AppCrashView to post further details about crashes. There's a link to that program here:

viewtopic.php?f=3&t=49

OK, here goes:

Code: Select all

Operating system: Windows 8.1
Browser version: 2018.01.05
64-bit
Problem URL: Crashes are completely random, but last visited was https://www.ghacks.net/2018/01/09/microsoft-security-updates-january-2018-release/
Theme: Soft Grey by mlathrom
Installed extensions:
Activate Reader View
Adblock Plus
Add to Search Bar   
BehindTheOverlay   
CanvasBlocker
Classic Theme Restorer
Close Tab By Double Click
Context Search
Decentraleyes
Element Hiding Helper for Adblock Plus
google-no-tracking-url
HTTPS Everywhere    2017.12.6
I don't care about cookies
No Coin - Block miners on the web!
No Resource URI Leak
NoSquint Plus
Privacy Badger
ReminderFox
Self-Destructing Cookies
Status-4-Evar
Thumbnail Zoom Plus
User-Agent Switcher
Video DownloadHelper
Installed plugins: Open H264 - Cisco
Widevine Content Description module
Flash 28.0.0.126 (disabled)


The following data was copied from AppCrashView

Code: Select all

Version=1
EventType=APPCRASH
EventTime=131600530404722912
ReportType=2
Consent=1
UploadTime=131600577381395316
ReportIdentifier=7079475c-f5ef-11e7-bfeb-0c54a51289ad
IntegratorReportIdentifier=7079475b-f5ef-11e7-bfeb-0c54a51289ad
NsAppName=basilisk.exe
Response.BucketId=bbc7bb569daec06aa9c1ebc704db4b3d
Response.BucketTable=4
Response.LegacyBucketId=1856023761465854781
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=basilisk.exe
Sig[1].Name=Application Version
Sig[1].Value=4.0.2.6579
Sig[2].Name=Application Timestamp
Sig[2].Value=5a4edfe7
Sig[3].Name=Fault Module Name
Sig[3].Value=xul.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=4.0.2.6579
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5a4ee6bb
Sig[6].Name=Exception Code
Sig[6].Value=80000003
Sig[7].Name=Exception Offset
Sig[7].Value=00000000021af9ad
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a9ef
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a9eff186869426676f98145a36f1a188
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=b9c3
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=b9c3869682816973c9a0b73aa7075f98
UI[2]=C:\Program Files\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\Basilisk\basilisk.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:\Program Files\Basilisk\mozglue.dll
LoadedModule[5]=C:\WINDOWS\system32\ADVAPI32.dll
LoadedModule[6]=C:\Program Files\Basilisk\MSVCP140.dll
LoadedModule[7]=C:\Program Files\Basilisk\VCRUNTIME140.dll
LoadedModule[8]=C:\Program Files\Basilisk\api-ms-win-crt-string-l1-1-0.dll
LoadedModule[9]=C:\Program Files\Basilisk\api-ms-win-crt-stdio-l1-1-0.dll
LoadedModule[10]=C:\Program Files\Basilisk\api-ms-win-crt-environment-l1-1-0.dll
LoadedModule[11]=C:\Program Files\Basilisk\api-ms-win-crt-runtime-l1-1-0.dll
LoadedModule[12]=C:\Program Files\Basilisk\api-ms-win-crt-math-l1-1-0.dll
LoadedModule[13]=C:\Program Files\Basilisk\api-ms-win-crt-locale-l1-1-0.dll
LoadedModule[14]=C:\Program Files\Basilisk\api-ms-win-crt-heap-l1-1-0.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[17]=C:\Program Files\Basilisk\api-ms-win-crt-convert-l1-1-0.dll
LoadedModule[18]=C:\WINDOWS\system32\msvcrt.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[20]=C:\WINDOWS\system32\RPCRT4.dll
LoadedModule[21]=C:\Program Files\Basilisk\api-ms-win-crt-multibyte-l1-1-0.dll
LoadedModule[22]=C:\Program Files\Basilisk\api-ms-win-crt-time-l1-1-0.dll
LoadedModule[23]=C:\Program Files\Basilisk\api-ms-win-crt-filesystem-l1-1-0.dll
LoadedModule[24]=C:\Program Files\Basilisk\api-ms-win-crt-utility-l1-1-0.dll
LoadedModule[25]=C:\WINDOWS\system32\SspiCli.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
LoadedModule[27]=C:\Program Files\Basilisk\ucrtbase.DLL
LoadedModule[28]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[29]=C:\Program Files\Basilisk\nss3.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[32]=C:\WINDOWS\system32\WS2_32.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[34]=C:\WINDOWS\system32\USER32.dll
LoadedModule[35]=C:\WINDOWS\system32\NSI.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[38]=C:\WINDOWS\system32\GDI32.dll
LoadedModule[39]=C:\WINDOWS\system32\IMM32.DLL
LoadedModule[40]=C:\WINDOWS\system32\MSCTF.dll
LoadedModule[41]=C:\Program Files\Basilisk\lgpllibs.dll
LoadedModule[42]=C:\Program Files\Basilisk\xul.dll
LoadedModule[43]=C:\WINDOWS\system32\SHELL32.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\USP10.dll
LoadedModule[45]=C:\WINDOWS\system32\ole32.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[48]=C:\WINDOWS\system32\CRYPT32.dll
LoadedModule[49]=C:\WINDOWS\system32\SHLWAPI.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[51]=C:\WINDOWS\system32\SETUPAPI.dll
LoadedModule[52]=C:\WINDOWS\system32\WINTRUST.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[54]=C:\WINDOWS\system32\OLEAUT32.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\pdh.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[59]=C:\WINDOWS\system32\MSASN1.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[63]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[65]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[67]=C:\WINDOWS\system32\propsys.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\Dnsapi.dll
LoadedModule[69]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[70]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[71]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[72]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[73]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[74]=C:\WINDOWS\system32\wshbth.dll
LoadedModule[75]=C:\Program Files\Basilisk\softokn3.dll
LoadedModule[76]=C:\Program Files\Basilisk\nssdbm3.dll
LoadedModule[77]=C:\Program Files\Basilisk\freebl3.dll
LoadedModule[78]=C:\Program Files\Basilisk\nssckbi.dll
LoadedModule[79]=C:\WINDOWS\System32\Wpc.dll
LoadedModule[80]=C:\WINDOWS\System32\NETAPI32.dll
LoadedModule[81]=C:\WINDOWS\system32\Normaliz.dll
LoadedModule[82]=C:\WINDOWS\System32\wevtapi.dll
LoadedModule[83]=C:\WINDOWS\System32\netutils.dll
LoadedModule[84]=C:\WINDOWS\System32\srvcli.dll
LoadedModule[85]=C:\WINDOWS\System32\wkscli.dll
LoadedModule[86]=C:\WINDOWS\System32\SAMCLI.DLL
LoadedModule[87]=C:\WINDOWS\SYSTEM32\d2d1.dll
LoadedModule[88]=C:\WINDOWS\SYSTEM32\XmlLite.dll
LoadedModule[89]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[91]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[92]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[93]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[94]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[95]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[96]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[97]=C:\Program Files\Acer\Acer Power Management\SysHook.dll
LoadedModule[98]=C:\WINDOWS\system32\COMDLG32.dll
LoadedModule[99]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[100]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17810_none_6240b9c7ecbd0bda\COMCTL32.dll
LoadedModule[101]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.18790_none_9333b10747484d36\gdiplus.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[107]=C:\WINDOWS\SYSTEM32\winhttp.dll
LoadedModule[108]=C:\Windows\System32\rasadhlp.dll
LoadedModule[109]=C:\WINDOWS\system32\explorerframe.dll
LoadedModule[110]=C:\WINDOWS\system32\DUser.dll
LoadedModule[111]=C:\WINDOWS\system32\DUI70.dll
LoadedModule[112]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[113]=C:\WINDOWS\system32\PSAPI.DLL
LoadedModule[114]=C:\Program Files\Basilisk\mozavutil.dll
LoadedModule[115]=C:\Program Files\Basilisk\mozavcodec.dll
LoadedModule[116]=C:\WINDOWS\system32\mfplat.dll
LoadedModule[117]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[118]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[119]=C:\WINDOWS\system32\mf.dll
LoadedModule[120]=C:\WINDOWS\system32\dxva2.dll
LoadedModule[121]=C:\WINDOWS\system32\evr.dll
LoadedModule[122]=C:\Windows\System32\MSAudDecMFT.dll
LoadedModule[123]=C:\Windows\System32\msmpeg2vdec.dll
LoadedModule[124]=C:\WINDOWS\system32\twinapi.dll
LoadedModule[125]=C:\WINDOWS\system32\Bcp47Langs.dll
LoadedModule[126]=C:\WINDOWS\system32\LINKINFO.dll
LoadedModule[127]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\cscapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Basilisk
AppPath=C:\Program Files\Basilisk\basilisk.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=632B1F6B7E60D92714640C6BCC3F029A

I always disable Flash and only re-enable it if I site requires it (which is hardly ever).

There's also a Report.wer file. Do you want that as well? If so, where do I have to upload it to?
Last edited by Hitchhiker on Wed, 10 Jan 2018, 15:12, edited 1 time in total.

User avatar
New Tobin Paradigm
Banned user
Banned user
Posts: 4417
Joined: Tue, 09 Oct 2012, 19:37

Re: Basilisk crashing daily

Postby New Tobin Paradigm » Wed, 10 Jan 2018, 16:16

The only one that stands out is: LoadedModule[97]=C:\Program Files\Acer\Acer Power Management\SysHook.dll

Can you uninstall Acer Power Management and see if that resolves your crashes?
I hate Pod Six. Tch, I don't even know why we have a Pod Six. Total suck Pod.
[ ニュー・トビン・パラダイム ]

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Re: Basilisk crashing daily

Postby Hitchhiker » Wed, 10 Jan 2018, 17:18

New Tobin Paradigm wrote:The only one that stands out is: LoadedModule[97]=C:\Program Files\Acer\Acer Power Management\SysHook.dll

Can you uninstall Acer Power Management and see if that resolves your crashes?

No offence, but I'm loathe to do that. I don't think it's a power management issue somehow because I can run complex games like Crysis and don't experience any crashes.

Also, this same problem appears to have cropped up a few times on Firefox: https://support.mozilla.org/en-US/questions/1047038
The advice there has been to disable h/w acceleration, but on my system that's already disabled. I think what I'll do is try the opposite i.e. enable it.

Also, I have WebGL disabled in about:config since it's been flagged as a security risk: https://security.stackexchange.com/ques ... ty-concern What's your opinion on that? Does Basilisk isolate the risk? I've just re-enabled it to see if it makes any difference. Mozilla seems to take the view that it needs to be enabled: https://support.mozilla.org/en-US/kb/up ... celeration

User avatar
New Tobin Paradigm
Banned user
Banned user
Posts: 4417
Joined: Tue, 09 Oct 2012, 19:37

Re: Basilisk crashing daily

Postby New Tobin Paradigm » Wed, 10 Jan 2018, 17:43

Well it is the only suspect of a third party lib being injected into the application.. As I said.. The error code indicates a manual/hardcoded breakpoint.. Our code doesn't have breakpoints like that. Thus, it MAY be the cause, unless I missed another dll being injected into the runtime out of the 100 or so listed.

But that's fine.. You go on complaining about crashes when you are not willing to try and see what is actually causing it.

Maybe someone else can help you...
I hate Pod Six. Tch, I don't even know why we have a Pod Six. Total suck Pod.
[ ニュー・トビン・パラダイム ]

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21163
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Basilisk crashing daily  Topic is solved

Postby Moonchild » Wed, 10 Jan 2018, 18:08

Basilisk does have some manual breakpoints which are deliberate crashes.

The crash at that address specifically is a browser shutdown not finishing, and instead of hanging indefinitely, the browser triggers a crash itself to terminate the process.
i.e.: the crash occurred when you exited the browser.
This not exiting is often caused by injected modules, so the suggestion that that foreign module is to blame was definitely something to consider.
Otherwise, it may be one of your extensions, as well.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Re: Basilisk crashing daily

Postby Hitchhiker » Wed, 10 Jan 2018, 18:18

Moonchild wrote:Basilisk does have some manual breakpoints which are deliberate crashes.

The crash at that address specifically is a browser shutdown not finishing, and instead of hanging indefinitely, the browser triggers a crash itself to terminate the process.
i.e.: the crash occurred when you exited the browser.
This not exiting is often caused by injected modules, so the suggestion that that foreign module is to blame was definitely something to consider.
Otherwise, it may be one of your extensions, as well.

Well, that's a much more gentlemanly response that the previous one by New Tobin Paradigm.

The reason I don't want to uninstall the power management tool is because I have an Optimus system i.e. there are two video cards in the same machine. According to the Acer documentation, the power management tool handles switching power between modules according to application being run.

But I'll try switching to both Firefox ESR and Waterfox over the next couple of days to determine if the problem repeats itself or not with those two.

Thanks for your input Moonchild.

User avatar
Moonraker
Keeps coming back
Keeps coming back
Posts: 861
Joined: Wed, 30 Sep 2015, 23:02
Location: Lincolnshire.UK.

Re: Basilisk crashing daily

Postby Moonraker » Wed, 10 Jan 2018, 20:41

New Tobin Paradigm wrote:Well it is the only suspect of a third party lib being injected into the application.. As I said.. The error code indicates a manual/hardcoded breakpoint.. Our code doesn't have breakpoints like that. Thus, it MAY be the cause, unless I missed another dll being injected into the runtime out of the 100 or so listed.

But that's fine.. You go on complaining about crashes when you are not willing to try and see what is actually causing it.

Maybe someone else can help you...

In other words you yourself dont know the cause and being rude to users is your way out of it so to speak.
middle age creeping upon you perhaps.?
Linux Lite 3.6 64bit.
Pale moon 27.9.0

User avatar
New Tobin Paradigm
Banned user
Banned user
Posts: 4417
Joined: Tue, 09 Oct 2012, 19:37

Re: Basilisk crashing daily

Postby New Tobin Paradigm » Wed, 10 Jan 2018, 22:42

Off-topic:
Moonraker wrote:In other words you yourself dont know the cause and being rude to users is your way out of it so to speak.
middle age creeping upon you perhaps.?


The fact is.. My information was slightly out of date.. So there is one case of a manual breakpoint which Moonchild explained. One of the FEW reasons that could be the the injected dll that to me stood out. It may also be an extension that isn't playing nice.. Still, Moonchild doesn't exactly know.. You going to target him too? Would only be fair. In any event, that is why I asked if they could try to eliminate that hooked in module as a possibility.. They refused.. So I said what I said.. The OP already commented on that and I considered the matter over with..

So why are you trying to start up an argument? You do know I am only 32 right? Also, are you aware of exactly how much I have done around here despite dropping my official status and self important title over people like you? I was even asked to stop posting and I obeyed the soft ban for just under six months again because of people like you.

Well, I want to be on generally good terms with forum-land but that isn't always going to be the case in every situation.. However, I am back in full.. You really are gonna have to learn to live with that. The REASON is that I am needed around here and I need to BE around here.. What I don't need is THIS.

You sure are glad to use the fruits of my unpaid .. and indeed personally funded resources and labor but damn if I can't have an opinion. Get over it dude and please don't derail topics on the forum for personal attacks.

Despite all that.. I hope you can resolve your personal issues with me and have a good rest of your night.

On irc.freenode.net #palemoon wrote:[20180110.1243-50] <NewTobinParadigm> viewtopic.php?f=61&t=17967&p=131919#p131914
[20180110.1244-14] <NewTobinParadigm> I should stick to just spouting the obvious in speeches and not do support
[20180110.1250-17] <MoonchildPM> NewTobinParadigm: given the crash offset and symbols, it's possible to backtrace. Basilisk probably has manual breakpoints as in deliberate crashes.
[20180110.1250-26] <MoonchildPM> I'll have a look what code sits at that address
[20180110.1250-41] <NewTobinParadigm> oh.. well shit
[20180110.1251-01] <NewTobinParadigm> i didn't know it had manual breakpoints.. cause Tycho doesn't..
[20180110.1251-05] <NewTobinParadigm> alright
[20180110.1251-20] <MoonchildPM> Tycho does but only for OOM, really.
[20180110.1252-00] <NewTobinParadigm> let me guess. i am TOTALLY out of date and that was only true on 26
[20180110.1252-12] <NewTobinParadigm> that has annoyingly been happening lately
Last edited by New Tobin Paradigm on Wed, 10 Jan 2018, 22:48, edited 6 times in total.
I hate Pod Six. Tch, I don't even know why we have a Pod Six. Total suck Pod.
[ ニュー・トビン・パラダイム ]

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21163
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Basilisk crashing daily

Postby Moonchild » Wed, 10 Jan 2018, 23:22

Also, for the record, back-tracing from a crash address to a code point without a crashdump is annoying, time-consuming, and can only be done if the build symbols (.pdb) are available as well as the exact build that crashed. It involves launching VS, launching the browser, attaching the debugger to the running process, getting the crashed module base address from VS (since ASLR will load it at a different base address every time), manually adding the crash offset to the base address with a hex calculator, breaking the program's execution, entering the resulting base+offset address in VS, and then seeing at which point in the code that address takes you.
Even with that, you still won't have a call stack so it's only good for very specific, static crash points, which this happened to be.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

User avatar
Moonraker
Keeps coming back
Keeps coming back
Posts: 861
Joined: Wed, 30 Sep 2015, 23:02
Location: Lincolnshire.UK.

Re: Basilisk crashing daily

Postby Moonraker » Thu, 11 Jan 2018, 10:26

New Tobin Paradigm wrote:
Off-topic:
Moonraker wrote:In other words you yourself dont know the cause and being rude to users is your way out of it so to speak.
middle age creeping upon you perhaps.?


The fact is.. My information was slightly out of date.. So there is one case of a manual breakpoint which Moonchild explained. One of the FEW reasons that could be the the injected dll that to me stood out. It may also be an extension that isn't playing nice.. Still, Moonchild doesn't exactly know.. You going to target him too? Would only be fair. In any event, that is why I asked if they could try to eliminate that hooked in module as a possibility.. They refused.. So I said what I said.. The OP already commented on that and I considered the matter over with..

So why are you trying to start up an argument? You do know I am only 32 right? Also, are you aware of exactly how much I have done around here despite dropping my official status and self important title over people like you? I was even asked to stop posting and I obeyed the soft ban for just under six months again because of people like you.

Well, I want to be on generally good terms with forum-land but that isn't always going to be the case in every situation.. However, I am back in full.. You really are gonna have to learn to live with that. The REASON is that I am needed around here and I need to BE around here.. What I don't need is THIS.

You sure are glad to use the fruits of my unpaid .. and indeed personally funded resources and labor but damn if I can't have an opinion. Get over it dude and please don't derail topics on the forum for personal attacks.

Despite all that.. I hope you can resolve your personal issues with me and have a good rest of your night.

On irc.freenode.net #palemoon wrote:[20180110.1243-50] <NewTobinParadigm> viewtopic.php?f=61&t=17967&p=131919#p131914
[20180110.1244-14] <NewTobinParadigm> I should stick to just spouting the obvious in speeches and not do support
[20180110.1250-17] <MoonchildPM> NewTobinParadigm: given the crash offset and symbols, it's possible to backtrace. Basilisk probably has manual breakpoints as in deliberate crashes.
[20180110.1250-26] <MoonchildPM> I'll have a look what code sits at that address
[20180110.1250-41] <NewTobinParadigm> oh.. well shit
[20180110.1251-01] <NewTobinParadigm> i didn't know it had manual breakpoints.. cause Tycho doesn't..
[20180110.1251-05] <NewTobinParadigm> alright
[20180110.1251-20] <MoonchildPM> Tycho does but only for OOM, really.
[20180110.1252-00] <NewTobinParadigm> let me guess. i am TOTALLY out of date and that was only true on 26
[20180110.1252-12] <NewTobinParadigm> that has annoyingly been happening lately

There was no offence intended and i apologise if you took it that way.However this is not the palce to discuss the merits and weaknesses of peoples characters.Lets hope the issue is resolved and does not revolve into personal criticism.
Linux Lite 3.6 64bit.
Pale moon 27.9.0

dodona
Apollo supporter
Apollo supporter
Posts: 33
Joined: Mon, 18 Dec 2017, 08:50

Re: Basilisk crashing daily

Postby dodona » Sun, 14 Jan 2018, 16:23

I confirm Basilisk crashing daily for linux. I can reproduce it by surfing in some web sides, in most others not. Again libxul is involved. See backtrace:
{ "signal": 11
, "executable": "/opt/basilisk/basilisk-bin"
, "stacktrace":
[ { "crash_thread": true
, "frames":
[ { "address": 140579913853211
, "build_id": "f29e9a2fffb96f32a469aba89c8a7eb1bc9ba8b0"
, "build_id_offset": 76059
, "function_name": "raise"
, "file_name": "/lib64/libpthread.so.0"
}
, { "address": 140579677732239
, "build_id": "b460a924978036b73196cd4dfe4a25b444fbdf4f"
, "build_id_offset": 48393615
, "file_name": "/opt/basilisk/libxul.so"
}
, { "address": 140579691357825
, "build_id": "b460a924978036b73196cd4dfe4a25b444fbdf4f"
, "build_id_offset": 62019201
, "file_name": "/opt/basilisk/libxul.so"
}
, { "address": 140579913853568
, "build_id": "f29e9a2fffb96f32a469aba89c8a7eb1bc9ba8b0"
, "build_id_offset": 76416
, "file_name": "/lib64/libpthread.so.0"
}
, { "address": 140579688761525
, "build_id": "b460a924978036b73196cd4dfe4a25b444fbdf4f"
, "build_id_offset": 59422901
, "file_name": "/opt/basilisk/libxul.so"
}
, { "address": 140579687267550
, "build_id": "b460a924978036b73196cd4dfe4a25b444fbdf4f"
, "build_id_offset": 57928926
, "file_name": "/opt/basilisk/libxul.so"
}
, { "address": 5621906551131
, "build_id_offset": 5621906551131
} ]
Last edited by dodona on Sun, 14 Jan 2018, 16:24, edited 1 time in total.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21163
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Basilisk crashing daily

Postby Moonchild » Sun, 21 Jan 2018, 15:22

dodona: that information is completely useless.
Also, in any stacktrace you have, you'll undoubtedly find mention of libxul, because that is where most of our code lives.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

Hitchhiker
Apollo supporter
Apollo supporter
Posts: 32
Joined: Sun, 10 Dec 2017, 11:06
Location: The Netherlands

Re: Basilisk crashing daily

Postby Hitchhiker » Mon, 22 Jan 2018, 21:14

Just a quick update on this issue - I'm the OP - I switched to using Waterfox for a few days and then came back to using Basilisk again. Since then there haven't been anymore crashes.

The only change I made was to uninstall the Nvidia drivers I was using even though they're the latest version v390.65 (which addresses the Meltdown/Spectre vulnerabilities in Nvidia GPUs incidentally) in Windows Safe Mode and then reinstall them again. Other than that though, nothing else has been changed.

Anyway, I'm pleased Basilisk is back to normal again.


Return to “Basilisk”

Who is online

Users browsing this forum: No registered users and 3 guests