Sandboxie software compatibility bug + a crash report

-sandboxie is based on Sbiedll injection if the software requires loading a driver in kernel mode, then it won't work under Sandboxie anyway. Sandboxie does not allow driver loading because it would be effectively impossible to sandbox.

-Sandboxie is completely open source

-TOR 32bit

-Description
-Path of the failed application :	C:\Program Files\Sandboxie\SbieCtrl.exe

-Signature of the problem
-Event name of the problem :	APPCRASH
-Name of the application:	SbieCtrl.exe
-Application version:	5.49.0.0
-Timestamp of the application:	6041428c
-Default module name:	StackHash_68be
-Default module version:	6.3.9600.16408
-Default module timestamp:	523d5305
-Exception Code:	c0000374
-Shifting the exception:	PCH_9A_FROM_ntdll+0x0000000000096B2A
-System version:	6.3.9600.2.0.0.768.101
-Additional information n° 1:	68be
-Additional information n° 2:	68bead46096368e6f28690972ccdc53c
-Additional information n° 3:	cda3
-Additional information n° 4:	cda3a157b184d2f730e63ecc1e702131

-Description
-Path of the failed application :	C:\Program Files\Sandboxie\SbieSvc.exe

-Signature of the problem
-Event name of the problem :	APPCRASH
-Name of the application:	SbieSvc.exe
-Application version:	5.49.0.0
-Timestamp of the application:	60414258
-Default module name:	StackHash_1131
-Default module version:	6.3.9600.16408
-Default module timestamp:	523d5305
-Exception Code:	c0000374
-Shifting the exception:	PCH_9A_FROM_ntdll+0x0000000000096B2A
-System version:	6.3.9600.2.0.0.768.101
-Additional information n° 1:	1131
-Additional information n° 2:	1131385d577431abb9a53fb7d9a9a21a
-Additional information n° 3:	8d81
-Additional information n° 4:	8d8148e144cfbabfcf6467e169dfdda6

• cda3a157b184d2f730e63ecc1e702131 SbieCtrl.exe.10000.dmp
• New_text__5_.txt
• SbieSvc.zip

changed the description

changed the description

changed the description

changed the description

Does Firefox work under Sandboxie?

added Needs Information label

changed the description

Yes https://github.com/sandboxie-plus/Sandboxie/issues/538

I also wanted to quote : #30660 (comment 2663538)

TOR asks me one time only if I want the pages in English

Someone reported on IRC that it also affects the 64 bit version.

removed Needs Information label

added Bug label

Personally I can reproduce this conflict with Sandboxie only in x64 versions of Tor Browser (including the latest 11.0.10), not in the x86 versions.

Compatibility tests:

According to my tests, the first Tor Browser 64-bit version to introduce the conflict with Sandboxie is torbrowser-install-win64-8.0a9_en-US.exe

The previous Tor Browser 8.0a8 x64 version doesn't have this issue, so it could be considered the latest working 64-bit version that is compatible with Sandboxie.

Requirements to reproduce the issue:

Operating system: Windows 10 x64 21H1 or 21H2

Sandboxie Plus 1.0.15 x64

Any build of Tor Browser 64-bit, except Tor Browser 8.0a8 x64 or below versions

Reproducible steps:

1. Install any build of Tor Browser 64-bit (except Tor Browser 8.0a8 x64 that seems the latest working one)
2. Download Sandboxie Plus 1.0.15 x64 and install it
3. Run the main executable SandMan.exe
4. Go to Options menu -> Edit ini file -> confirm yes
5. Find AutoRecover=y line below [DefaultBox] and replace it with AutoRecover=n (just to avoid the annoying recovery popup)
6. Save the ini file with Notepad and close it
7. Right-click on "Start Tor Browser" shortcut -> open the "Run Sandboxed" context menu entry
8. At some point, during its startup, I get the following error message:

9. Even if you press OK twice to dismiss it, the browser will still launch anyway, but with the about:page tab that stays blank. When trying to load a web page in a new tab, the tab also stays blank.

Note 1: Mozilla Firefox is completely unaffected and can be run in Sandboxie without issues.

Note 2: Sandboxie's source code is available at https://github.com/sandboxie-plus/Sandboxie

Note 3: Tor Browser 8.0a9 changelog: https://blog.torproject.org/new-release-tor-browser-80a9

Possible culprits

Bug 26239Bug 24197: Enable content sandboxing for 64bit Windows builds

Note 4: I asked for help on the #tor IRC channel, so I have new interesting findings.

In short, this Sandboxie crash also applies to some non-standard Firefox x64 builds that use the same mingw-w64 toolchain of Tor Browser x64 builds:

Extract of #tor channel conversation

tor: #40371 (closed) - Sandboxie software compatibility bug + a crash report

isaak654: Sandboxie developer already looked at it, and he states it's something you need to fix about content sandboxing in x64 builds

GeKo: yeah

GeKo: providing a patch would be much appreciated

GeKo: investigating that is likely to be non-trivial

isaak654: indeed, the last working Tor Browser release with Sandboxie is win64-8.0a8 (released in 2018), so I think it's time starting to find an interested developer

GeKo: i suspect the problem is that we use a different compiler for windows binaries than mozilla by default

GeKo: however, you can verify that as mozilla is providing firefox build with the same toolchain

GeKo: let me find a Firefox x64 link for you to try

GeKo: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/RKlEsB7ETXSlpOh4SWYc7Q/runs/0/artifacts/public/build/target.zip

GeKo: you could try the bundle you get in target.zip

GeKo: i bet you have the same issue with sandboxie

GeKo: even though it's plain firefox code

isaak654: I can reproduce the Sandboxie issue with that Firefox Nightly x64 build too, and now?

GeKo: the next steps for you or anyone debugging this could be checking whether that happens with the debug version as well and/or whether newer/older compiler versions fix the problem

GeKo: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/WsXatyNiRUWKG6TSUDbOaw/runs/0/artifacts/public/build/target.zip has the binaries for the debug build

isaak654: the Firefox debug build you passed me crashes the same, no change

GeKo: great

GeKo: now the excitment starts

GeKo: the debug build has debug symbols. someone should attach a debugger to it and then figure out what's going on

GeKo: OR someone could start bisecting the compiler/toolchain figuring out what is going on

GeKo: pick your poison :)

GeKo: fwiw, the ticket you wanted to link to is likely https://bugzilla.mozilla.org/show_bug.cgi?id=1461421

GeKo: we know, though, that this is not a tor browser issue

GeKo: it happens with firefox, too, provided you use the same non-official toolchain

GeKo: feel free to update the tor-browser ticket too with what you learned :)

Note 5: The bug was fixed with the release of Sandboxie v1.0.21 / 5.55.21

removed

Enable content sandboxing for 64bit Windows builds looks a likely culprit, but who knows :)

It appears that the Sandboxie developer has demonstrated the involvement of Tor Browser 64-bit content sandboxing, especially in the last line of his comment: https://github.com/sandboxie-plus/Sandboxie/issues/538#issuecomment-787092834

Hopefully Tor developers will take a look at the reproducible steps I posted above.

thanks for being snarky, and apologies for helping then, I will remove my post

I am not a native English speaker and I didn't consider my clarification to your post would be interpreted as a complaint against you. The clarification was made to dissipate any potential doubt about the involvement of Tor Browser 64-bit content sandboxing.

I never thought you weren't helpful, at the same time this bug needs extra help to reproduce those steps to find the exact cause. I would appreciate if you could restore your previous post, thank you.

Apologies to any subscribers for the noise

@isaak654 , I can't restore my old comment, it is gone. The thing is, this ticket has been here for over a year with no dev activity. The first thing with bugs, is to provide consistent steps to reproduce, and if possible, a regression. This saves devs a lot of time.

Nowhere in this ticket was there any reference to a regression, so I provided the changelog, with hyperlinks, and suggested a possible culprit, so that a dev can easily and quickly use that information, rather than wading though some external chatter (which I never bothered to read). Took me five minutes of my valuable time.

All this, so that perhaps the ticket might get resolved or at the very least spark something, to help YOU. But now it's too late, I already removed it and it is GONE for good. Unsubscribing. Enjoy your issue

All this, so that perhaps the ticket might get resolved or at the very least spark something, to help YOU. But now it's too late, I already removed it and it is GONE for good. Unsubscribing. Enjoy your issue

I wish you all the best and hope you find that there is no reason to hold a grudge (even using words in caps) over a trivial misunderstanding. :-)

Returning to this bug, I added a note 3 in order to recover partially the deleted post.

Added Note 4 with a new update about this issue.

I also informed the current Sandboxie developer DavidXanatos who replied that debugging mingw-w64 toolchain will definitely require a lot of work.

Good news, DavidXanatos has included a fix for this issue in Sandboxie v1.0.21 / 5.55.21 and it works fine on my end.

I would like to thank the Tor developer @gk for pointing us in the right direction.

I would like to thank the Tor developer @gk for pointing us in the right direction.

You are welcome. Time to close this issue I guess.

closed

If it's not something to fix in mingw-w64, then yes.

May 6th : https://github.com/sandboxie-plus/Sandboxie/issues/538#issuecomment-1119831708

I have investigated the issue further and found the problem, it will be fixed in one of the upcoming builds

also - see the comment two up - #40371 (comment 2801957)

and it works fine on my end

+1 closing @richard PS: is there a need/want for adding an External label? I am a klutz, it was already closed

There is also a Sandboxie isue at #32412 (closed) which is 2 years old, NI if it still applies, the title could do with a cleanup anyways