Closed
Bug 474801
Opened 17 years ago
Closed 17 years ago
Checking for MaybeGC conditions when allocating GC things in JS shell
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: andrei, Assigned: andrei)
References
Details
(Keywords: fixed1.9.1, Whiteboard: fixed-in-tracemonkey)
Attachments
(2 files, 3 obsolete files)
22.07 KB,
patch
|
Details | Diff | Splinter Review | |
16.51 KB,
patch
|
igor
:
review+
|
Details | Diff | Splinter Review |
This is part 1 of the original bug 453432. It adds "MaybeGC" conditions check for allocation of GC thins, but it does not remove the MaybeGC functionality for DOM objects.
Assignee | ||
Comment 1•17 years ago
|
||
Assignee: general → andrei
Attachment #358201 -
Flags: review?(igor)
Updated•17 years ago
|
Attachment #358201 -
Flags: review?(igor) → review+
Comment 2•17 years ago
|
||
landed to tm - http://hg.mozilla.org/tracemonkey/rev/6657640cbbb2
Assignee | ||
Comment 3•17 years ago
|
||
Attachment #358201 -
Attachment is obsolete: true
Attachment #358409 -
Flags: review?(igor)
Comment 4•17 years ago
|
||
(In reply to comment #3)
> Created an attachment (id=358409) [details]
> Updated patch
As discussed with Andrei a possible reason for tinderbox failures with the previous patch was subtle changes in the frequency of cycle collector runs. The patches replaces the explicit tracking of the number JS_GC calls with using JSRuntime.gcNumber exposed through a new API. But that means that JS_GC calls done outside nsJSEnvironment, like JS_GC done from the cycle collector itself, or JS_GC called when destroying JSContext, would also contribute to the counter.
Effectively it may make nsJSRuntime::sGCCount to run faster leading to more frequent cycle collections. It principle it may explain the crash test timeout. It may also explain the mochitest leak as the cycle collector may not run at the proper moment that test expects.
Now, the new version tries to offset that faster nsJSRuntime::sGCCount rate with ignoring at least the GC runs done during the cycle collection. It could be enough to offset that rate effect so I would try to land the updated patch again.
Updated•17 years ago
|
Attachment #358409 -
Flags: review?(igor) → review+
Assignee | ||
Comment 5•17 years ago
|
||
Attachment #358409 -
Attachment is obsolete: true
Attachment #359034 -
Flags: review?(igor)
Assignee | ||
Comment 6•17 years ago
|
||
Previous patch was made in mozilla-central instead of tracemonkey
Attachment #359034 -
Attachment is obsolete: true
Attachment #359053 -
Flags: review?(igor)
Attachment #359034 -
Flags: review?(igor)
Comment 7•17 years ago
|
||
Given the instability of tinderbox tests I prefer to play safe here. So I would try to land the patch without nsJSEnvironment changes related to the sGCCounter.
Attachment #359062 -
Flags: review+
Comment 8•17 years ago
|
||
landed to TM - http://hg.mozilla.org/tracemonkey/rev/799649d4e416
Whiteboard: fixed-in-tracemonkey
Comment 9•17 years ago
|
||
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 10•16 years ago
|
||
Keywords: fixed1.9.1
Updated•16 years ago
|
Flags: in-testsuite-
Updated•16 years ago
|
Attachment #359053 -
Flags: review?(igor)
You need to log in
before you can comment on or make changes to this bug.
Description
•