Closed
Bug 1144973
Opened 10 years ago
Closed 10 years ago
js::StringifySavedFrameStack doesn't put the string in the cx's compartment like it promises
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla39
Tracking | Status | |
---|---|---|
firefox39 | --- | fixed |
People
(Reporter: fitzgen, Assigned: fitzgen)
References
Details
Attachments
(1 file, 2 obsolete files)
4.27 KB,
patch
|
fitzgen
:
review+
|
Details | Diff | Splinter Review |
It's documentation says:
> The stringified stack out parameter is placed in the cx's compartment.
*Sigh*, but that just is not true.
The first thing it does is maybe enter the SavedFrame's compartment and then the string is built in that possibly different compartment.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8579711 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 2•10 years ago
|
||
Sorry, I know you aren't doing reviews right now, but you broke this in 04f34e86aee1 and this is a pretty small patch :P
Assignee | ||
Comment 3•10 years ago
|
||
Comment 4•10 years ago
|
||
Comment on attachment 8579711 [details] [diff] [review]
Ensure that StringifySavedFrameStack puts its stack string in the cx's compartment
This works, but couldn't we actually just let the AutoMaybeEnterFrameCompartment go out of scope before calling finishString()? Seems to me like that would work fine (albeit with a bit more dependency on StringBuffer internals) and avoid the wrap() call. Maybe I'm just allergic to wrap() calls: they show up in profiles too much. :(
Either way should document near the opening curly of the scope we're adding what the scope is there for.
Attachment #8579711 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8579711 -
Attachment is obsolete: true
Attachment #8579712 -
Attachment is obsolete: true
Attachment #8580147 -
Flags: review+
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Nick Fitzgerald [:fitzgen] from comment #6)
> Try push:
> https://treeherder.mozilla.org/#/jobs?repo=try&revision=17c29e1ad7d1
Those failures are fixed in bug 1144108.
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 8•10 years ago
|
||
Keywords: checkin-needed
Comment 9•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
You need to log in
before you can comment on or make changes to this bug.
Description
•