Hi to all I recently updated to Firefox 110, and noticed some oddities with jerky graphics with some games. I assumed it was a Sandboxie issue as I only run browsers using Sandboxie Classic. I didn't notice any graphics related problems with Firefox 109.01. I just learned today that in Firefox version 110, they introduced "GPU Sandboxing" as a security feature. Nice feature but is causing some issues, one with XMBC (X-Mouse Button Control) mouse scrolling, etc. My issue as mentioned was with some graphics in games being jerky, not all just some. As I was reading about this feature, I saw an article how to disable this feature. After disabling this new feature in Firefox, smooth graphics returned while running inside Sandboxie, no jerky gaming or graphics. Made sense to me to disable it, as it may be conflicting with running the browser already sandboxed with Sandboxie Classic which is what I use, 5.62.2. It was just something worth trying and it worked for me to disable this new Firefox feature. Thought I would bring this up to this section in case anyone else found their graphics processing a bit jerky and assuming it is Sandboxie. It isn't, it just appears to be a feature within Firefox that might conflict with some other software or devices, perhaps this will assist David also in future builds to address if necessary. I have not read much about any conflicts with this new Firefox feature other than the one mentioned about XMBC mouse button control...maybe my problem has not been experienced yet or potential other issues? Here is the instruction on how to disable this feature in Firefox...if YOU choose to do so. I did for the above mentioned reasons. Hope this may help someone...many may not be affected, I was, so here is the info that helped me. Have a great week ahead! Link to instructions: https://techdows.com/2023/02/disable-gpu-sandboxing-firefox.html
please stop that not helpful working in about prefs. in special this undermines firefox security https://www.wilderssecurity.com/threads/firefox-gpu-sandboxing-and-slow-startup.450590/ same as always: dont know- dont do it! users are definitely not aware of consequences. and you need to read the forum first before submitting false tips.
Sorry Brummelchen. Did you read the article? The instructions were for about:config that users often go into to solve issues they may be having. At the end of the instruction how to disable, it states clearly Mozilla doesn't recommend turning it off, of course they don't, but you can if it causes issues. Please read before accusing someone of breaking forum rules. Mods are free to delete this post if that is the case, I only meant to help someone who may have had the same problem I did or bring it up in case this feature caused issues with other software. I disabled it because I am already running Firefox sandboxed and having the GPU sandboxed slowed gaming. Disabling solved the problem of jerky graphics while running browser using Sandboxie as stated. THIS FEATURE DID NOT WORK WITH MY BROWSER SANDBOXED, IT CONFLICTED WITH SANDBOXIE IN MY CASE. NOT SANDBOXIE FAULT. THIS WAS MY WORKAROUND FOR ME. "Recently, Mozilla launched Firefox with GPU Sandboxing enabled by default on Windows. The feature had a conflict with the third-party Windows program and broke mouse wheel scrolling in Firefox. If you’re affected by one or more such issues, you can disable GPU Sandboxing in Firefox" What is GPU Sandboxing? GPU Sandbox boosts Firefox security even further. It isolates the GPU process from other processes and makes it difficult for malware to target other processes. The feature has its benefits and drawbacks. Mozilla has mulled over activating GPU sandbox In Firefox on Windows over several years as it may result in graphical glitches, performance issues, or others. While the company is aware of the issue there was a conflict between X-Mouse Button Control and Firefox GPU Sandbox that breaks wheel mouse scrolling, the organization has gone ahead and released Firefox 110. We have been surprised by the number of users reported about the wheel scrolling issue. While there is not yet data or reports available if Firefox’s GPU Sandboxing causing other issues if there are any, you can disable the feature. I stated that this solved my problem, and thought giving instructions how to disable this new feature was helpful. MODS: Please remove my post if it broke forum rules...I see nothing in it that would have broken any rules...had the article link been read, it is clear some are having issues, I was with some games, and I found this as a solution. I apologize to anyone I offended, I thought I was being helpful.
Yes, some have problems with it, some have not. This is helpful for those who have the issue w/the new gpu sandboxing feature. When I first read the changelog for Firefox 110 in another forum, the first thing that occurred to me was any possible interactions between that and Sandboxie (I use Plus here). So far, I've not had anything. But that doesn't preclude anyone else from experiencing problems. I've had issues w/hardware acceleration in Firefox before and others in the same context have not. No worries.
For now the GPU process on Windows still has access to the whole filesystem anyway: https://www.ghacks.net/2023/01/17/firefox-110-will-launch-with-gpu-sandboxing-on-windows/
i dont care about questionable third party articles while i get my informations from sources or insiders. this feature collides with sandboxie which is not ready to handle this feature. and there is NO comparison to other (graphical) features possible - this is sandboxing and not graphics related. for the german audience, entry in about:support: "Ebene der isolierten Umgebung des GPU-Prozesses" Brinkman pionts it out vice versa this means that exist malware for real which is able to abuse the gpu process and more. hint: chrome and similar are already using a gpu sandbox.
I use Firefox 110 only since yesterday. So far I realized no conflicts with Sandboxie. But in case that there were any conflicts between Firefox' GPU Sandboxing and Sandboxie: what should a user do? In this case disabling GPU Sandboxing (as described by Jim1cor13) would be my preferred solution. Simply because I trust that the protection offered by Sandboxie is more essential than the new protection given by Firefox' new feature. With "this feature" you mean "GPU Sandboxing"? If yes, what would you suggest in this case? To disable the feature or to disable Sandboxie? Or simply to hope for a quick fix by David?
as linked David works on 1.80 which include a fix. but again: gambling around with browsers security - questionable.
@Jim1cor13 Thank You! Recently I ditched long-used FF, the first graphic would be instant, if the graphics below the first one, took minutes to load. You sol may be worth a try. Now using Edge, FF has features, you can place on the toolbar for ease, Edge is in some ways more cumbersome. If fixed via update I may try FF again. Or it could be something else with FF. Edge same graphics load now, FF minutes
You're very welcome Rico! Glad I could help, it was just something I found that worked for me when the graphics became jerky in some situations, games, etc. My issues were not so much the loading of graphics, but the frames were jerky, while playing, etc., not within videos, but within some HTML5 applications. Happy to hear you found the information potentially useful.