Currently we always try to create our synchronization texture. We shouldn't to this on D3D11 WARP on Windows 7 because this will fail and put our D3D11 WARP device in an invalid state.

When using WARP D2D is disabled by default anyway. Since creating the sync texture will fail on Windows 7. For now let's not create one anywhere since this patch will need uplifting.

Bug 1130788 was an e10s m6, updating this bug to reflect this.

[Tracking Requested - why for this release]: This is a really bad bug. And it exists in 37 as well. It's hard to say for how much trouble this is responsible on 37, but it affects all Win7 users that are blacklisted for D3D11 as far as I can tell :(.

I don't have the numbers, but we do get bugs with blacklisted Windows 7, and WARP and we do get the undocumented "out of memory" errors which suggest we're hitting this bug in other places, so we really do want to get this uplifted as high as it can go. If we don't have time for 37, can we line it up for 37.0.1 if that happens?

Tracking this across the board. We're too late for 37 if we still want to release on time. Please let me know if you think this is bad enough to warrant holding the release. I have tracked this bug for 37 so that it will be on the list for consideration for a point release if one is necessary. In that case we will need to evaluate the risk that the fix causes other breakage against the impact of this bug on the user population in 37.

I think we need a few days with the fix on the other channels, so I'd say this needs to wait for the dot release if it happens.

(In reply to Lawrence Mandel [:lmandel] (use needinfo) from comment #9) > Tracking this across the board. > > We're too late for 37 if we still want to release on time. Please let me > know if you think this is bad enough to warrant holding the release. > > I have tracked this bug for 37 so that it will be on the list for > consideration for a point release if one is necessary. In that case we will > need to evaluate the risk that the fix causes other breakage against the > impact of this bug on the user population in 37. It's complicated.. if apparently we're happy with the quality of 37. Let's just ship it. It is a bad bug for the 37 population, but the beta population has already been living with this bug.

This hasn't landed anywhere yet, right?

Bas, is this something we should release note?

Comment on attachment 8583574 [details] [diff] [review] Do not attempt to create a sync texture when using WARP Approval Request Comment [Feature/regressing bug #]: [User impact if declined]: Blocked configurations of Windows 7 (either blocklisted or vmware, remote desktop, etc.) will freeze. [Describe test coverage new/current, TreeHerder]: [Risks and why]: [String/UUID change made/needed]: Just to be clear - "aurora" refers to 38, "beta" to 37. We know it won't be 37, but as it's tracked, readying in case there is a 37.0.1.

Comment on attachment 8583574 [details] [diff] [review] Do not attempt to create a sync texture when using WARP As the merge is ongoing, I am doing to take it for beta (38) and marking "?" for release (37).

(In reply to Milan Sreckovic [:milan] from comment #14) > Bas, is this something we should release note? In theory it shouldn't cause 'user-facing' issues. So I'm not sure there's something sensible we could put in a release note. The idea of this causing additional instability for affected users is purely theoretical and we don't know what exactly the symptoms of that would be.

This fix is too risky to take in release. I'm marking 37 as wontfix. We'll target 38.

(In reply to Lawrence Mandel [:lmandel] (use needinfo) from comment #20) > This fix is too risky to take in release. I'm marking 37 as wontfix. We'll > target 38. Very good decision, this fix causes bug 1150376!

Comment on attachment 8583574 [details] [diff] [review] Do not attempt to create a sync texture when using WARP Missed marking this as release- earlier.