Long CC times with large numbers of unloaded tabs

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
7 years ago
4 years ago

People

(Reporter: jesup, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Spun off from bug 720512 as a separate bug.

On a recent (3/3/2012) personal build of m-c, my 'big' profile is showing longish CC times (per comments by smaug) of 50-60ms, with 200-220ms GCs when idle, with this from about:tabs

(13.0a1 (2012-03-03), running since last Saturday night on a private pull & build)


781 tabs across 21 groups in 21 windows
29 tabs have been loaded

about:memory
1,203.41 MB ── resident
1,141.36 MB ── explicit
2,074.08 MB ── vsize

about 200MB system-principal; 50MB about:blank (unloaded tabs); 43MB plus.google.com, 23MB gmail; 283MB window-objects; 231MB (20%) heap-unclassified
(Reporter)

Comment 1

7 years ago
Created attachment 602931 [details]
about:memory (taken slightly later)
(Reporter)

Comment 2

7 years ago
Hmmpf, no easy way I see to log/save the error log data from the Error Console, or even copy anything except a single entry.


CC(T+137007.1) duration: 65ms, suspected: 3631, visited: 32127 RCed and 30545 GCed, collected: 3469 RCed and 178 GCed (3647 waiting for GC)
ForgetSkippable 19 times before CC, min: 6 ms, max: 38 ms, avg: 12 ms, total: 229 ms, removed: 9811

GC(T+137081.9) TotalTime: 219.2ms, Type: global, MMU(20ms): 0%, MMU(50ms): 0%, Reason: CC_WAITING, NonIncrementalReason: incremental permanently disabled, +chunks: 0, -chunks: 0
mark: 166.2, mark-roots: 14.5, mark-other: 20.7, sweep: 50.5, sweep-obj: 6.0, sweep-string: 0.5, sweep-script: 1.0, sweep-shape: 9.5, discard-code: 2.6, discard-analysis: 8.2, xpconnect: 7.6, deallocate: 0.2

Some GC's seem now to be shorter (always TOO_MUCH_MALLOC):

GC(T+137118.2) TotalTime: 111.8ms, Type: compartment, MMU(20ms): 0%, MMU(50ms): 0%, Reason: TOO_MUCH_MALLOC, NonIncrementalReason: incremental permanently disabled, +chunks: 0, -chunks: 0
mark: 81.8, mark-roots: 9.9, mark-other: 13.4, sweep: 28.0, sweep-obj: 3.5, sweep-string: 1.2, sweep-script: 0.1, sweep-shape: 3.8, discard-code: 0.3, discard-analysis: 0.6, xpconnect: 7.6, deallocate: 0.0

Comment 3

7 years ago
Could you create a cc log.
(the script in the first gray box https://wiki.mozilla.org/Performance:Leak_Tools#Cycle_collector_heap_dump)
If the urls don't contain anything privacy sensitive, I could try to analyze the log.

(with 21 windows open I expect most of the stuff in CC graph is just random chrome objects)

Comment 4

4 years ago
(In reply to Olli Pettay [:smaug] from comment #3)
> Could you create a cc log.
> (the script in the first gray box
> https://wiki.mozilla.org/Performance:Leak_Tools#Cycle_collector_heap_dump)
> If the urls don't contain anything privacy sensitive, I could try to analyze
> the log.
> 
> (with 21 windows open I expect most of the stuff in CC graph is just random
> chrome objects)
Flags: needinfo?(rjesup)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(rjesup)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.