Bugzilla

This is still in the queue for someone to debug, but we've been triaging it and are pretty sure it's related to async drawing changes in Firefox.  We did confirm that disabling async drawing in Firefox "resolves" the issue.  

I'm also wondering if the specific version of Win10 under test bears on the test results.  I'm definitely able to reproduce this under the latest moz-regression-gui on Windows, but I'm on Win10 10.0.16813 with Flash Player 32.0.0.321. 

I was able to narrow this down to a reasonably small range, but I couldn't pin it down to a specific changeset.  I did observe that there are some intermediate variations of "brokenness" to how the Flash content renders, where in some instances the SWF doesn't render at all, and in some instances, there's a HTML layer with troubleshooting instructions that overlays the top half of the SWF.  I called those "good" in the regression because they were drawing something, but I'm wondering if there are multiple intersecting issues in this Firefox build range. 

I've included the full log output from mozregression and an overview screenshot to help you reproduce my results.

This is still in the queue for someone to debug, but we've been triaging it and are pretty sure it's related to async drawing changes in Firefox.  We did confirm that disabling async drawing in Firefox "resolves" the issue.  

I'm also wondering if the specific version of Win10 under test bears on the test results.  I'm definitely able to reproduce this under the latest moz-regression-gui on Windows, but I'm on Win10 10.0.18363 with Flash Player 32.0.0.321. 

I was able to narrow this down to a reasonably small range, but I couldn't pin it down to a specific changeset.  I did observe that there are some intermediate variations of "brokenness" to how the Flash content renders, where in some instances the SWF doesn't render at all, and in some instances, there's a HTML layer with troubleshooting instructions that overlays the top half of the SWF.  I called those "good" in the regression because they were drawing something, but I'm wondering if there are multiple intersecting issues in this Firefox build range. 

I've included the full log output from mozregression and an overview screenshot to help you reproduce my results.

This is still in the queue for someone to debug, but we've been triaging it and are pretty sure it's related to async drawing changes in Firefox.  We did confirm that disabling async drawing in Firefox "resolves" the issue.  

I'm also wondering if the specific version of Win10 under test bears on the test results.  I'm definitely able to reproduce this under the latest moz-regression-gui on Windows, but I'm on Win10 10.0.18363 with Flash Player 32.0.0.321. 

I was able to narrow this down to a reasonably small range, but I couldn't pin it down to a specific changeset.  I did observe that there are some intermediate variations of "brokenness" to how the Flash content renders, where in some instances the SWF doesn't render at all, and in some instances, there's a HTML layer with troubleshooting instructions that overlays the top half of the SWF.  I called those "good" in the regression because they were drawing something, but I'm wondering if there are multiple intersecting issues in this Firefox build range that led to my inconclusive bisection attempt.

I've included the full log output from mozregression and an overview screenshot to help you reproduce my results.