With 'javascript.options.mem.log' enabled GC status messages are broken

RESOLVED FIXED in mozilla14

Status

()

Core
JavaScript Engine
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: billm, Assigned: billm)

Tracking

({regression})

unspecified
mozilla14
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 606021 [details] [diff] [review]
fix

We're passing a wide in as a %s argument, so only the first character appears.
Attachment #606021 - Flags: review?(terrence)
Comment on attachment 606021 [details] [diff] [review]
fix

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

Whoops!  Thanks for fixing this.  I really should have checked more thoroughly after changing that to an nsString at the last minute.
Attachment #606021 - Flags: review?(terrence) → review+
(Assignee)

Comment 2

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/09f0b5bc3301
Target Milestone: --- → mozilla14
Duplicate of this bug: 735994
Blocks: 531396
Status: NEW → ASSIGNED
Keywords: regression
Summary: javascript.options.mem.log is broken → With 'javascript.options.mem.log' enabled GC status messages are broken
https://hg.mozilla.org/mozilla-central/rev/09f0b5bc3301
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.