Closed Bug 1159810 Opened 9 years ago Closed 9 years ago

Kill full gc timer when gc starts


(Core :: DOM: Core & HTML, defect)

36 Branch
Not set





(Reporter: smaug, Assigned: smaug)




(1 file)

Attached patch v1Splinter Review
We have similar Kill*Timer calls in nsJSContext::GarbageCollectNow.
Attachment #8599403 - Flags: review?(continuation)
Comment on attachment 8599403 [details] [diff] [review]

Review of attachment 8599403 [details] [diff] [review]:

Oh, PreciseGCRunnable::Run() starts a GC by directly calling JSAPIs.  Fun.
Attachment #8599403 - Flags: review?(continuation) → review+
I guess we want this on FxOS v2.2 as well?
well, if this helps with the testing. In practice this shouldn't affect actual behavior too much.
tryserver is a bit orange. Most of the failures are known, but not all :/
I'll land this to m-i.  For some reason also that previous try push had quite a few known failures.
Hopefully this isn't making try more flaky (though that would mean we have some bugs in the tests).
Not just Android debug reftest-8, final tally looks more like 1, 2, 3, 4, 7, 8 which probably means "any of them if you happen to hit them right." Impossible to say whether you had any similar effect on Android debug mochitests, since you landed on top of a patch which made them fail to start and infinitely retry, so it'd be a good idea to include them in the try push where you check whether you've stopped randomly killing Android debug reftests.
Sorry about that.

Looks like fixing this isn't really worth.

For we should just make
PreciseGCRunnable to use the normal GC triggering methods.
Closed: 9 years ago
Flags: needinfo?(bugs)
Resolution: --- → WONTFIX
Depends on: 1161491
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.