Closed Bug 992324 Opened 8 years ago Closed 8 years ago

disable interruptible reflow in reftest


(Testing :: Reftest, defect)

Not set


(Not tracked)



(Reporter: dbaron, Assigned: dbaron)



(2 files)

I was discussing the corrupted-image reftest failures like bug 930894 with seth, and one theory we came up with was that reflow might be being interrupted.

This would only happen if:
 * something thinks there are pending user events, which is plausible, though probably shouldn't be happening

 * clock skew is causing the interrupt timer to decide to interrupt really quickly, which is also plausible on a VM (and those failures are only happening on the B2G desktop VMs)

Given the lack of pending user events, reftest normally wouldn't be testing interruptible reflow.  So we should probably just explicitly disable interruptible reflow in the reftest harness.  (If we wanted to leave it, we would want to make the state machine in MakeProgress wait for all interruptible reflows to complete, but given that we normally wouldn't expect this to ever happen, it seems better to just disable it.)
Unless I'm missing something, we don't have any prefs to disable interruptible reflow, only env vars.  Is that right?  And are you ok with me adding a pref?
Flags: needinfo?(bzbarsky)
You're correct, and adding a pref sounds just fine.  I can't recall now why we did this with env vars instead of prefs to start with.
Flags: needinfo?(bzbarsky)
Without this patch, mInterruptsEnabled is frequently (although not
always) initialized to true in nsPresContext::ReflowStarted while
running reftests; with the patch it is always initialized to false.
Attachment #8404328 - Flags: review?(bzbarsky)
Comment on attachment 8404327 [details] [diff] [review]
patch 1 - Add a pref to disable interruptible reflow

Attachment #8404327 - Flags: review?(bzbarsky) → review+
Comment on attachment 8404328 [details] [diff] [review]
patch 2 - Disable interruptible reflow in reftest harness

Attachment #8404328 - Flags: review?(bzbarsky) → review+
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
You need to log in before you can comment on or make changes to this bug.