Closed
Bug 1300834
Opened 6 years ago
Closed 6 years ago
DOM GC slice logging should say, for each slice, whether the slice is in the content or chrome process
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla51
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
Details
Attachments
(1 file)
1.39 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
Even better might be to have separate prefs for the two.... but that's a bigger change, and not as obviously desirable.
![]() |
Assignee | |
Comment 1•6 years ago
|
||
Attachment #8788547 -
Flags: review?(bugs)
![]() |
Assignee | |
Updated•6 years ago
|
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Comment 2•6 years ago
|
||
Comment on attachment 8788547 [details] [diff] [review] GC slice logging should say what process the slice is for (another unrelated thing which would be nice is to reduce the number of GC slices logged to the console. We don't need to log almost all of them. Just got 74 in a row)
Attachment #8788547 -
Flags: review?(bugs) → review+
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ff96cb069ef2 GC slice logging should say what process the slice is for. r=smaug
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ff96cb069ef2
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Updated•3 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•