Recommended Posts

IGC does make overall responsiveness better , opening/closing tabs/scrolling is faster IMO

Am I the only one who thinks that JS performance should, almost exclusively, not dictate rendering/scrolling/flash performance?

Scrolling is done in native code in Firefox, but pages can register JS callbacks for each scroll event, so the JS event loop is intertwined with the main event loop, you can't separate them.

Edit: And that's just scrolling, there's a bunch of other things as well.

Hadn't noticed that the 'PDF Viewer' add-on had been updated recently. The new UI looks great and it loads PDFs very quickly, it's a lot better than the Adobe plug-in. One thing I would like is the ability to choose a 'hand' cursor where you can click and drag the document rather than just the text cursor.

Hadn't noticed that the 'PDF Viewer' add-on had been updated recently. The new UI looks great and it loads PDFs very quickly, it's a lot better than the Adobe plug-in. One thing I would like is the ability to choose a 'hand' cursor where you can click and drag the document rather than just the text cursor.

It still seems to be factor slower than Adobe Reader - I mean like comparing n vs n^4 slower at rendering PDFs.

Adobe Reader downloads the PDF and displays it almost instantly after downloading it.

PDF JS for some reason renders the PDF one word/line at a time which takes way longer - and it does it again when zooming.

This is completely unacceptable.

If you don't like it then just disable it, and you can keep using Acrobat.

It's not even meant to be enabled by default, the user has to do that.

All I had to do is disable Adobe Reader to enable it

So it is enabled by default as long as you don't have a PDF reader plugin.

It also seems to be very RAM heavy.

https://bugzilla.moz...g.cgi?id=715376

This will improve overall responsiveness even a lot more by suspending activity in background tabs! Not only that , it will also use lesser CPU times and Memory

Try it out : https://addons.mozil...ackground-tabs/

It's not going to suspend background tabs, it's just going to be smarter at performing work in them.

Currently it stops event handlers and such firing faster than 1 second in background tabs, but if you have multiple tabs open and they're out of sync (due to each page having it's own timer), you could get into a situation where each timer firing directly after another timer, so the browser is still constantly processing events and timers. What they eventually want is a event queue, where each timer or event in every tab is added to a global list, and every second or so it goes through and processes all queued events, allowing it to do other work for the rest of the time (page rendering, etc.)

Edit: The addon does suspend background tabs, but that's as a proof of concept.

Azure Content Hardware Acceleration in Inbound.

Applying Updates in Background landed in Nightly.

Debugger Dev Tool is coming as turned ON in Nightly.

Off the Main Threading Compositing landed for Linux in Nightly.

I went to the about window and it downloaded an update then it said "restart to install" so I clicked that and firefox's window closed and nothing happened, I then checked task manager and firefox had shot up to using 13.5GB RAM out of 16GB so my computer was sitting at 15.8GB, this was a fresh profile with no addons. I had to kill firefox.exe, this kinda surprised me! That was some huge memory leak.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now