Closed Bug 1489155 Opened 6 years ago Closed 6 years ago

[Facebook] Trying to play Slotomania leads to tab crash

Categories

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

x86
Windows 7
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox62 --- unaffected
firefox63 --- fix-optional
firefox64 --- fix-optional

People

(Reporter: mberlinger, Unassigned)

Details

(Keywords: regression, regressionwindow-wanted)

[Affected versions]:
- latest Nightly 64.0a1 (BuildId 20180905223809)
- Beta 63.0b3 (BuildId 20180904170936)

[Unaffected versions]:
- Release 62.0 (BuildId 20180830143136)

[Affected platforms]:
- Windows 7x32

[Unaffected platforms]:
- Windows 10x64
- mac OS

[Steps to reproduce]:
1. Launch Firefox.
2. Login on Facebook.
3. Access the following link: https://apps.facebook.com/169545139744270
4. Click to start playing.

[Expected result]:
- The game successfully loads.

[Actual result]:
- The tab crashes.

[Regression range]:
This seems to be a regression.

I'll investigate this further as soon as time permits.

[Additional notes]:
Please note that the actual result is, somehow, intermitent because:
- Sometimes the crash occurs as soon as the game starts loading.
- Sometimes the crash occurs after the game is played for a while (1-2 minutes of gameplay).

Please note that most of the crashes were silent (no crash id's were generated) but after further investigating this issue (crashing the page several times), a crash report was successfully generated: crash id: e5d0b41e-41f3-4186-bd46-f896d0180906
The crash report is [@ OOM | small ] - which basically is an out of memory situation.
Priority: -- → P2
Yes, not much can be done for a 32-bit Windows OOM.
Priority: P2 → P5
Marking fix-optional for 64. We could still take a patch in 65.
Marking as wontfix as this is a non actionable P5 and we already have multiple bugs tracking [@ OOM | small ] crashes.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.