I don't like encouraging mucking around in about:config, but I might as well mention this one. If you don't mind your window losing vibrancy and rounded corners, you should be able to significantly improve battery life on macOS by setting "gfx.compositor.glcontext.opaque" to true. This makes WindowServer stop drawing whatever is behind the Firefox window. This bug tracks the proper solution: https://bugzilla.mozilla.…
I have a new 2018 MBP with an i9. I've noticed I can squeeze upwards of six hours battery out of it using Safari. With Firefox I'm lucky to get three. I made this change just to see. So far it does appear to have lowered the energy impact score a bit, but I'm not sure it's enough to matter yet. I guess we'll know in a couple hours. Edit: 20 minutes in and I've watched my Time Remaining estimate creep up from 3 hours…
Firefox about:config privacy settings
41–50 of 154 posts
Re: Firefox about:config privacy settings
#42what are the reasons for disabling memory and disk cache, and lowering dns caching?
Re: Firefox about:config privacy settings
#43Re: Firefox about:config privacy settings
#44config.trim_on_minimize = true Reduce memory usage when minimized. (Windows only) -This really helped for me
https://bugzilla.mozilla.org/show_bug.cgi?id=660367
// Our internal trim prevention logic is effective on 2K/XP at maintaining
// the working set when windows are minimized, but on Vista and up it has
// little to no effect. Since this feature has been the source of numerous
// bugs over the years, disable it (sTrimOnMinimize=1) on Vista and up.Re: Firefox about:config privacy settings
#45I don't like encouraging mucking around in about:config, but I might as well mention this one. If you don't mind your window losing vibrancy and rounded corners, you should be able to significantly improve battery life on macOS by setting "gfx.compositor.glcontext.opaque" to true. This makes WindowServer stop drawing whatever is behind the Firefox window. This bug tracks the proper solution: https://bugzilla.mozilla.…
I have a new 2018 MBP with an i9. I've noticed I can squeeze upwards of six hours battery out of it using Safari. With Firefox I'm lucky to get three. I made this change just to see. So far it does appear to have lowered the energy impact score a bit, but I'm not sure it's enough to matter yet. I guess we'll know in a couple hours. Edit: 20 minutes in and I've watched my Time Remaining estimate creep up from 3 hours…
Re: Firefox about:config privacy settings
#46I frequently see recommendations to disable "safe browsing" features. Why?
Re: Firefox about:config privacy settings
#47Earlier quoted context omitted.
I have a new 2018 MBP with an i9. I've noticed I can squeeze upwards of six hours battery out of it using Safari. With Firefox I'm lucky to get three. I made this change just to see. So far it does appear to have lowered the energy impact score a bit, but I'm not sure it's enough to matter yet. I guess we'll know in a couple hours. Edit: 20 minutes in and I've watched my Time Remaining estimate creep up from 3 hours…
2018 MBP with i9 here as well. I am getting 10-11 hours battery life with Chrome. What exactly are you doing on your machine other than browsing as it isn't the browser causing such low battery life. Even when working in Xcode and IntelliJ I still easily get 7-8 hours.
Re: Firefox about:config privacy settings
#48I frequently see recommendations to disable "safe browsing" features. Why?
Re: Firefox about:config privacy settings
#49Good grief that's a long list. I'd rather just use a browser like Brave with privacy and ad blocks enabled by default.
Re: Firefox about:config privacy settings
#50I find that these accumulated lists of security ideas are usually dangerous - in any domain, not just Firefox or browsers. They collect information and misinformation and add a veneer of legitimacy. Some settings don't behave as you think; some aren't documented; some are poorly implemented or tested by the vendor, who didn't design them for end users, and their malfunctions can create more security holes. Some are implemented for reasons you don't understand ('before you tear down a fence, know the reason it was put there'). Some are dependencies for other settings, features, and subsystems.
It would have to be work by an expert in browsers or Firefox or security, such as a Mozilla engineer or someone like Giorgio Maone, for me to trust a list like this one.