DOM GC slice logging should say, for each slice, whether the slice is in the content or chrome process

RESOLVED FIXED in Firefox 51

Status

()

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Status:
RESOLVED FIXED
Opened:
3 years ago
Updated:
4 months ago

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Tracking

Version:
Trunk
Target:
mozilla51
Points:
---

Firefox Tracking Flags

(firefox51 fixed)

Details

Attachments

(1 attachment)

GC slice logging should say what process the slice is for
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: nobody → bzbarsky
Status: NEW → ASSIGNED
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
https://hg.mozilla.org/mozilla-central/rev/ff96cb069ef2
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox51: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.