AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Sandboxie plus github12/31/2023 In fact it does NOT! Currently I have no idea how I could have gotten this wrong initially?!:oops:įact is that current production-version of Opera v.80 is the last one that will run sandboxed with HW-acceleration=ON. Unfortunately I'v been premature in reporting that the latest upgrade to Sanboxie_Plus v.0.9.8 would already fix the newly discovered problems wit advanced Opera_developer-browser v.82. Since Opera v.80 (and also with HW-acceleration=off) the installation-process itself will no longer succeed with a target-folder being force-sandboxed - as has been possible with previous Opera-versionsįurther update about this issue by algol1: ![]() So the question remains what the hell they may have "improved" again with that latest version to cripple the HW-acceleration-functionality within Sandboxie?Īlso do you have any educated guess how much disabling HW-acceleration will cost performance-wise?Īnd since HW-acceleration DID WORK within Sandboxie up until now - how are the odds any minor adaptions could implement into Sandboxie would make HW-acceleration=on possible within Sandboxie again?Īddendum: Now that with HW-acceleration=off the browser will start sandboxed again I should point out that the first phenomenon described above still persists. It really did the trick! I wasn't even thinking of that - as until Opera v.80 all had worked well with HW-acceleration enabled. Use hardware acceleration when available" -> try off. ![]() Workaround with one caveat (even with HW acceleration=off, the installation-process itself will no longer succeed with a target-folder being force-sandboxed as with previous Opera-versions): These observations - just in case that matters - have again been made on an 11th-gen-Intel-machine but currently I have no reason to assume that the phenomena described wouldn't occur on any Win10-system upgrading to these latest Opera-versions. Good thing we meanwhile have that "panic key" as this (terminating the process) for now seems the only way to close down that unresponsive window. To make things worse the advanced "Developer versions" opera v.81 (using Chromium engine v.95) and latest v.82 won't install sandboxed any longer either - but even when initially installed outside a sandbox first and running without problems outside - will later refuse to open within a sandbox.Īll I will get is a white screen, no sandboxie-error-msg, and after a few seconds a message in the header-bar saying "Loading. ![]() New production version v.80 (using Chromium engine v.94) will no longer install sandboxed, albeit when installed normally first (without forced-Sandbox-folder) can later be opened sandboxed as normal and will perform without issues. There is a another report related to Opera version 80 that won't work with hardware-acceleration enabled:
0 Comments
Read More
Leave a Reply. |