1299204 - Force GC/CC in reftests since we can't figure out why nothing works

Status: RESOLVED FIXED

(Core :: JavaScript: GC, defect)

Description

[Terrence Cole [:terrence]]

Attachment: force_gc_cc_in_reftests-v0.diff

This is a last resort. Things that fix the problem for me locally time out on try and hacks that hide the problem on try quadruple my test times locally. Hopefully just forcing a GC/CC occasionally will keep the overheads low enough that tests can at least complete everywhere while we investigate the root cause. At least, it worked for me when I tried it a month ago.

Comment 1

[Mason Chang [Inactive] [:mchang]]

Comment on attachment 8786396 [details] [diff] [review]
force_gc_cc_in_reftests-v0.diff

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

::: layout/tools/reftest/reftest-content.js
@@ +45,1 @@
>  

nit: add a comment saying this runs for both the content and parent process. We had a comment in the other CC bug. Thanks!

Comment 2

[Terrence Cole [:terrence]]

https://hg.mozilla.org/integration/mozilla-inbound/rev/4558fc3a712042f288ed2999bbc55410dfe4a224
Bug 1299204 - Do GC and CC even more aggressively in reftests; r=mchang

Comment 3

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/4558fc3a7120