Honestly, it's hard to say exactly at this point, because I hadn't used AF much under Linux before installing it. As compared to TFF under OSX, its flying, but I think it was noticeably quicker before installing FoxPep (To be clear I had FoxPep installed on TFF as well). I'd say it's slightly slower than LeopardWebkit at this point, but obviously way more stable. I also am wondering if I'm realizing all the benefits, because I'm suspicious that 2D acceleration isn't working correctly atm, so I'm about to post in the Remix thread about that.@dbdjre0143 How does it drive?
@MacFoxG4 Well... that's just unexpected. Every browser on every platform I've ever tested, including AF on SL, has never crashed at a YouTube video, and by all accounts have been much improved with zero drawbacks.
Scanning through 1.9.2's engine configuration, I could find nothing that should ever cause that to happen.
My best guess is that Arctic Fox is so niche of an implementation and is such a rapidly aging Frankenstein of a browser, it (the latest version, at least) cannot handle whatever kind of reasonable load it has to deal with when modified, self evidenced by its crashing and freezing on many different SL installs (many times I've experienced myself) even when in a totally stock state.
It was my fault to recommend foxPEP with that.
Go ahead and remove the patch, and make a new preferences file. Assuming it was not the cause of the crash, if you set media.webm.enabled to false in about:config, you should still be able to get the smoother video playback (720p) nonetheless.
I would say maybe try TenFourFox FPR23 instead of Arctic Fox. foxPEP should work much better with it than the latter.
Please accept my apologies for the inconvenience.
I would advise against any messing around in about:config and/or using an additional prefs file when it comes to AF, SW or IW browsers. They are all based on Pale Moon code, therefor they are not firefox. The code is similar, but different. The PM dev team already tweaked the stock prefs file to work best with these changes. I personally don't change anything (except maybe a user agent override) from default on those browsers and have no issues. On intel there is really is no reason to tweak anything. Those machines are more than powerful enough that they don't need the extra help. As @z970mp mentioned in an old post awhile back, don't try to tweak AF's prefs with Firefox tweaks. It will implode. It's not Firefox. It's close because it's based on mozilla code, but there are thousands if not millions of lines of code different between the two. I'd only suggest experimenting with prefs if you have a slow machine that struggles, otherwise the default settings are default for a reason.
Typically only an ad blocker (custom hosts file recommended) and script blocker (noscript/umatrix) are all that's needed for a pleasant experience. Also all 3 of the above browsers (AF/SW/IW) are compiled without webrtc, geolocation, neckowifi etc that PEP tries to disable (because they aren't disabled in TFF or regular FF), so that portion of the custom prefs is rendered mostly useless. Everyone has their own way they like to set things up, and i find the less you mess with a browser, the better it works. Too many prefs changes and too many add-ons/extensions, in my testing, slows a browser down vs what many think will speed it up. However, everyones setup, and browsing style is different, so your mileage will vary. Use what works best for you. Me.. only a custom hosts file to block ads, some form of script blocker (usually noscript, if i even bother installing a script blocker) and grease monkey (for various tasks). Thats it. No more, no less, and if you've seen my youtube videos, you'll notice how quick and smooth they all browse even on G4 machines.
Cheers
Too many prefs changes and too many add-ons/extensions, in my testing, slows a browser down vs what many think will speed it up.
New horizons await!
what will happen to our beloved PPC browser tweaks starting with this release (OSX and Linux variants)?
Does 2.0 feel slightly less responsive than 1.9, mainly in total loading times?
Quick question to anyone listening:
Does 2.0 feel slightly less responsive than 1.9, mainly in total loading times? Including a delay for page painting was a last minute decision and was done on the theoretical basis of making content render faster because the system wouldn't have to bother updating the window with each new packet, but on every system I've demoed, it doesn't make actually make any real world difference and only contributes to making the browser feel slower instead of faster, especially on modern machines.
That said, any comments, suggestions, complaints, or other input given either here or at GitHub is always appreciated.
Have not had any issues with this. I really think TenFourFox should have this by default.
FoxPep+TenFourFox+ublock origin+Transmission+CorePlayer is a wonderful combination and really pushing these machines into this decade for me.