Closed Bug 892405 Opened 11 years ago Closed 11 years ago

In GC logging, print Max Pause Time first, not Total Time

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla25

People

(Reporter: mccr8, Assigned: mccr8)

Details

Attachments

(1 file)

It is confusing.  I thought I had a bug on this, but I don't see it.

Also, there's a typo in "Sweep Intital Shapes".
Attached patch fix it upSplinter Review
I just did a minimal fix here.  This means for non-incremental GC, we'll print the reason before the total pause time, but that doesn't seem too weird. I guess I can do the test twice so the reason is later if you want.
Assignee: general → continuation
Attachment #775259 - Flags: review?(terrence)
Comment on attachment 775259 [details] [diff] [review]
fix it up

Review of attachment 775259 [details] [diff] [review]:
-----------------------------------------------------------------

Seems fine to me. r=me
Attachment #775259 - Flags: review?(terrence) → review+
I assume this is not an API change, where other tools might be affected of?
(In reply to Henrik Skupin (:whimboo) from comment #4)
> I assume this is not an API change, where other tools might be affected of?

Correct! I do not expect this to be a problem for you, but I figured I would give a heads up just in case. Specifically, this would only affect a tool that depended on the order of the properties in the JSON objects.
Or on something containing the precise string "Sweep Intital Shapes" ;)
Thank you Terrence! It's appreciated. We will watch out for it.
https://hg.mozilla.org/mozilla-central/rev/a4c0795e4c36
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla25
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: