Chrome Extensions Crash

HiddenWindow

HiddenWindow

New member
Version 142.0.7444.176 (Official Build) (64-bit)
Windows 11 Pro, 24H2
SBIE PLUS 1.16.8

Since the latest forced auto-update to Chrome, it seems extensions now crash again when running in Sandboxie Plus. I have tried installing older SBIE PLUS (all the way down to 1.5X) same results.

The extensions (uBlock, MBAM, all of them) eventually crash within seconds of loading multiple pages.
Extensions do not load at all if I run Chrome sandboxed and then proceed to run incognito sandboxed.

Sandboxie Chrome Crash.png

On the other hand, extensions work fully in Firefox, in both regular and private window.
 
I was unaware that Chrome extensions were able to crash. There might be an incompatibility between the latest version of Chrome and Sandboxie, the developer has to address. Thank you for providing information for him to take a closer look.

Does the same also happen in a new, fresh sandbox?
 
bastik-1001 said:
I was unaware that Chrome extensions were able to crash. There might be an incompatibility between the latest version of Chrome and Sandboxie, the developer has to address. Thank you for providing information for him to take a closer look.

Does the same also happen in a new, fresh sandbox?
Click to expand...

Just created a clean and fresh sandbox with the same results.
 
I have suddenly started to have the problem of uBlock Origin and Bitwarden extensions crashing and getting flagged as corrupt in Edge. I updated to 1.16.9 from 1.16.8 to try and solve the problem but it didn't help. Edge seems to update itself, so I don't know when the last update took place. I've tried everything I could locate to remedy the situation, but the problem still persists.
Edge will start up with the extension located in the upper bar, but after opening a few pages the icons disappear and under Extension Management they should as "Corrupt".
 
Weasel said:
I updated to 1.16.9 from 1.16.8 to try and solve the problem but it didn't help.
Click to expand...

It appears that Sandboxie itself did not break this, but that Chrome and Edge (maybe all Chromium based browsers, once they adopt whatever the change was) changed something that is incompatible with what Sandboxie does. This needs to be addressed, but David might like seeing that this is not a side effect of changes in Sandboxie.

Thank you for mentioning that it occurred with Sandboxie Plus 1.16.8.
 
I’m not sure where to post this since I’ve seen other threads addressing the same problem.
I now have 2 PCs ,with multiple users each, successfully running Sandboxie v1.16.9 and Edge v144.0.3719.82. The extension problem is no longer an issue.
I ditched the “Edge” sandbox I had created long ago, and tried running Edge in the “DefaultBox” sandbox and it worked.
There are too many options for me to try and compare the two sandbox settings to find the differences, but I assume there is a custom setting in my old “Edge” sandbox (something not in the DefaultBox) that’s causing the problem.
 
Well, now the problem of corrupt extensions has returned on one the PCs.
No changes were made anywhere, the problem just started to re-occur.
 
I would like to add an addendum to this report.
There is now an issue where if you click on any extension, the entire Chrome browser shuts down (sandboxed).
 
bastik-1001 said:
Just for your information. The main website links to the file hosted on GitHub. Most of the time the main website is lagging behind on purpose.
Click to expand...

I see.
I installed 1.17.2 with the most up-to-date Chrome, and the issue persists.
Extensions not only crash over a period of a few "refreshes" as in the OP, but also they will crash the entire browser if I click on any of the extensions.
 
Try stopping and disabling Google Chrome related services, usually three:
Code: 
Google Chrome Elevation Service (GoogleChromeElevationService)
Google Updater Internal Service (GoogleUpdaterInternalService)
Google Updater Service (GoogleUpdaterService)
 
Mr.X said:
Try stopping and disabling Google Chrome related services, usually three:
Code: 
Google Chrome Elevation Service (GoogleChromeElevationService)
Google Updater Internal Service (GoogleUpdaterInternalService)
Google Updater Service (GoogleUpdaterService)
Click to expand...
I did that once to no avail, and it also screwed up my Chrome profile.
 
~ Chrome update =
I'm still losing Home button, On startup and Extensions. I've lost track. What's current thinking regarding three Chrome Services? What's current thinking How-To update Chrome without needing to rebuild Chrome profile.
Note: red box
 
Last edited:
I don't really know. Everything is fine on Windows 10 and chrome installed in my system not installed in a sandbox.
 
You must log in or register to reply here.
Back
Top