search

Eclipse-Community / r3dfox

r3dfox is a modern Firefox based web browser for Windows Vista & 7. SourceForge link for downloading with older browsers. https://sourceforge.net/projects/r3dfox/
https://eclipse.cx/projects/r3dfox
Other
234 stars 9 forks source link

Turning off the menu bar renders the browser unusable, crashes on launch #159

Closed Glossaryck closed 3 months ago

Glossaryck commented 3 months ago

I'm currently running r3dfox version 129.0.1 on Windows 7 Professional SP1 (fully updated to January 2020, non-ESU). On a new installation, I went to turn off the menu bar, and the browser crashes; after which it keeps immediately crashing on launch, rendering the browser unusable.

Crash log provided by Windows: Problem signature: Problem Event Name: APPCRASH Application Name: r3dfox.exe Application Version: 129.0.1.643 Application Timestamp: 66bb88b3 Fault Module Name: KERNELBASE.dll Fault Module Version: 6.1.7601.24545 Fault Module Timestamp: 5e0eb6bd Exception Code: c06d007e Exception Offset: 000000000000b87d OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: fabd Additional Information 2: fabddded1baaa1f0125084edf693bcbb Additional Information 3: df0e Additional Information 4: df0e87cf6c110c5315ed4db28df4892d

Glossaryck commented 3 months ago

Sometimes the browser comes up with this message telling me to launch it in Safe Mode, but it also immediately crashes on launch in Safe Mode. image

K4sum1 commented 3 months ago

I'm unable to replicate on any install, hardware or VM.

Someone else had a weird issue with crashing without ESU, and supposedly running as administrator fixed it. What happens if you try to run as admin?

Glossaryck commented 3 months ago

I'm unable to replicate on any install, hardware or VM.

Someone else had a weird issue with crashing without ESU, and supposedly running as administrator fixed it. What happens if you try to run as admin?

I did not immediately try to run the browser as admin, instead I went back to version 129.0-4 and the bug magically went away. I have since updated to 129.0.1 and the bug did not come back.