Closed Bug 1263593 Opened 9 years ago Closed 2 years ago

Page has very large paint times (~250ms)

Categories

(Core :: Graphics, defect, P3)

45 Branch
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: rob, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(3 files)

Attached file Firefox-Bug-Report.zip
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20160325004402 Steps to reproduce: In my support ticket system (Sirportly) when I receive an large/long email like a CSF firewall update email. Firefox slows down and crashes. I have downloaded the html page and removed additional files that didn't cause the bug. See attached. To reproduce... Open attached ff-crash.html & main.css file in Firefox 45.0.1. Actual results: When opening the page Firefox slows down and will crash on low spec computers. I have recorded the pages performance, see ff-recording.json. This shows 'Incremental GC' being called a lot which is not normally called. It is worth noting if there is another ticket merged into the CSF one then the performance issues don't occur... Expected results: The page should load fine...
Component: Untriaged → JavaScript: GC
Product: Firefox → Core
Flags: needinfo?(terrence)
Looking at the bundled profile: In the 1.7s where we are GCing, we're using ~25% of the CPU time, which is actually a bit better than the 30% or so we're aiming for. Unfortunately, the page's graphical needs are such that that takes another 25% of the time, followed by style at 20%, followed by "Gecko" at 10% and we're left with about 9% of the time remaining where the user's scripts can actually run. There are a few tasks that stretch on too long (100s of ms) in both style and GC, but things actually appear to be pretty well incremental between the various CPU hogs up until 2.5 seconds in. At this point, graphics lands on the CPU and doesn't get off until almost 10 seconds later. I'd guess that the majority of the perceived slowness is probably actually this chunk, rather than GC.
Component: JavaScript: GC → Graphics
Flags: needinfo?(terrence)
Attached the same page that was crashing but with an additional comment which seems to fix the issue. To help with debugging.
Rob, can you see if this is still an issue on Firefox Nightly? Your test page is extremely janky for me on release (Firefox 45), but on Nightly it is quite smooth. It looks like we fixed some big painting performance cliff somewhere along the line.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(rob)
Summary: Garbage collector slowing down and crashing browser → Page has very large paint times (~250ms)
Performance is back to normal in the nightly build. Attached performance recording to confirm.
Flags: needinfo?(rob)
A quick mozregression seems to point to Bug 1250947 as having fixed this.
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 2 years ago
Depends on: 1250947
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: