Firefox 106.x Compatybility workaround (please test)

I'm looking into implementing a proper fix for the firefox 106.x issue (not just a hack that happens to work), and i noticed that it seams that I can't reproduce the issue on my Windows 11 (25227.1000) VM.
Hence I wanted to ask you to run some tests with the option
FirefoxHack1=n
On windows 11 and report back if with the workaround disabled ff 106 still works fin on 11 hence if its a win 10 specific compatibility bug.

The thing is I need VS 2022 to build FF which I only have installed in the Win 11 VM, my regular win 10 VM has VS 2019, so before I spent to much time on setting a win 10 VS2022 VM up I wanted to make this inquery to see if its worth the afford. Or if its some special case that makes my win 11 VM work while others may not.

 

FF 106 is working fine for me, but happy to try to help. Does FirefoxHack1=n go into sandboxie.ini

 

yes you can set it globally or per sandbox

 

FF 106.0.1 works fine for me with FirefoxHack1=n and without! I set it just for the sandbox I normally use for FF - Security Hardened Sandbox.

Win11 v22H2 build 22623.870

 

The issue still occurs with "FirefoxHack1=n" even under Windows 11.

I start Firefox in a sandbox. Go to YouTube and click on a video. When the video starts, the familiar error message appears:

Code:

WerFault.exe (7708): SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 14 - WerFault.exe [FF000000]

After that I go to Bing and a second later Firefox crashes!

This does not always happen, but after stopping and restarting the Sandboxie service and emptying the sandbox, I can almost always reproduce the issue.


Windows 11 21H2 Build 22000.1098 (x64), Firefox 106.0.1 (x64), Sandboxie-Plus 1.5.0 > VM with VirtualBox 6.1.38

 

Ok interesting, thank you very much...

 

OK problem solved, seams that the token firefox gave to its worker process in sandboxie was missing privileges to access \KnownDll32\oleaut32.dll which caused this dll to not being able to load resulting in the worker process crashing.
The better fix will be included in build 1.5.1

 

Great that you were able to find the cause and that the issue will be fixed for good in the next version. Thanks a lot!

 

I updated Firefox Saturday to 106.01. Both my machine and my wifes, and we both began to experience a few crashes. I updated Sandboxie classic to the latest 5.60
and so far we have not had any issues with firefox. No more crashes since updating to 5.60. I know firefox had issues with certain AMD processors that were causing crashes,
that appeared to be the reason for the latest 106.01 update, but I think they opened a door to other issues while addressing the known issues with certain AMD processors.

Sandboxie 5.60 is so far stable and working well. Thank you David.

 

Today i updated Firefox to version 106.0.5, and now it can't start anymore under Sandboxie (without Sandboxie Firefox starts without problems). At the start of Firefox there comes a small error message windows "Couldn't load XPCOM".
Then i installed the Firefox-version to the older 106.0.3, which i always used before, and with this version there are no errors and all works well.
My OS is Windows 7 (64 Bit), Firefox is 106.0.5 (64 Bit), Sandboxie is Sandboxie-Plus 1.5.1

Edit: I could solve the problem now: After i downgraded Firefox to 106.0.3 with a complete install, i choosed to upgrade again to 106.0.5, after Firefox offered the update. And this time the error message does not appear, and Firefox can be used without problems again. I don't know, what the reason for the error was, but now it is gone.

 

Probably, a reboot would have solved the issue. If there is a next time after another Firefox update, try that before reinstalling.

Bo

 

for wth do you need to build Firefox?
there exist enough builds you can use.
and further - if you build your own you are away from original end users releases.

btw firefox is running fine in sandboxie classic 5.60.2, Windows 10 + 11 and Defender only.

probably a mix from inside and outside which do not match and never worked together. you cant update firefox in the box and expect it working like charm.

 

To be able to do testing and change thair code, to have own working debug symbols, etc...
and no by own build should be very close to the official build as its the same soruce and their recomended tool chain.

 

seriously ?
https://firefox-source-docs.mozilla...reporter/Using_the_Mozilla_symbol_server.html

 

i know those they seam not complete

 

then it may recommended helping them out.

 

Yesterday Firefox 106.0.5 was working fine, but this morning I get SBIE2227 (my sandboxes are located on a memory disk) which I dismiss as normal, BUT in my usual security hardened sandbox FF can no longer see my profile extensions and favourites.

I uninstalled SB completely, reinstalled and copied back my old ini files, but it made no difference. Setting the box type back to standard isolation and all is working as normal. I can live with this, but I don't think I made any changes.

SB 1.5.3; Windows 22H2 x64 (Insider Preview 10.0.22623.891 update 11/11/22)

 

I added FirefoxHack1=n, and now it's behaving normally, although initially it seemed to have no effect.
ANd now I've deleted FirefoxHack1=n and it's still working - I give up!