Affected versions

• 68.0b3
• 69.0a1(05-20-2019)

Affected platforms

• Windows 7x86

Steps to reproduce

1. Download and install latest stable release of Flash Player.
2. Launch FF and go to facebook.com.
3. Launch the following games: Slotomania,Caesars Slots,Bingo Blitz,House of Fun,Vegas Downtown Slots,World Series of Poker,Farmville 2

Expected result

• The games launch with no issues, no tab crashes, no hangs.

Actual results

• Upon launching any of the above mentioned games, the following behaviors can be noticed: the tab crashes, no content is displayed where the game should be, you can reach the game's menu, but cannot enter the actual action phase(infinite loading).

Regression range

• Will return with regression range ASAP.

Additional notes

• This issue does not occur for the 67.0 release.
• This issue does not occur on Windows 7x64 platform

Hello,

I managed to pull a regression range for this issue :
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b13f2b24ae625d16fdeeb61cdec10978c3c75638&tochange=9145204dc6e50fc1dc993934bc8dd919b9b9b0ee

However I am uncertain that any of this issues have any impact on this behavior on Windows 7x32 . If not, needinfo me and I will attempt to pull another regression.

I've tested in a VMWare image using 32-bit Win7, latest Nightly, latest Flash and I don't see a crash on Farmville 2. This would be an environment where there's no hardware accelerated rendering, and I don't have a 32-bit machine to test that.

Vlad, what kind of device were you testing on?

Hello,
The machine on which I have reproduced this issue has the following specs:
AMD FX(tm)-8320 Eight-Core Processor × 8 (3.50GHz)"
ATI Radeon 3000 Graphics (508 MB)
16GB RAM
Hope this helps

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Any crash reports generated as a result of this crash?

Is WebRender enabled by chance? If so, I could see bug 1546126 being possibly related from that push range given that this bug is 32-bit only?

But yeah, a crash report would also be helpful here.

Hello,

I have tried reproducing this issue again but with no success.

Games were working as they should, without any more of the described behaviors from Description so unfortunately I could no retrieve any crash report.

I will keep trying to reproduce this issue again until I am able to pull a crash report that will help us understand this issue better.

I'm going to call this fix-optional for 68 if we can no longer reproduce.