Open Bug 1340883 Opened 6 years ago Updated 8 months ago

[testday-20170217] FISSURE WebGL game completely unresponsive


(Core :: Graphics: CanvasWebGL, defect, P3)

52 Branch
Windows 10




(Reporter: ithompson4, Unassigned)




(Keywords: 64bit, reproducible, testcase, Whiteboard: [testday-20170217][gfx-noted])


(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170216105119

Steps to reproduce:

1. Download and install Firefox Firefox 52 Beta 7
2. Navigate to
3. Click on Fissure Image to enter game
4. When game instructions appear press on spacebar to initiate game.

Actual results:

1. Nothing happens. Game cannot be initiated

Expected results:

1. Game should have been activated and User can play it.
QA Whiteboard: [testday-20170217]
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Whiteboard: [testday-20170217]
Has STR: --- → yes
Component: Untriaged → Canvas: WebGL
Priority: -- → P3
Product: Firefox → Core
Hi, which GPU and driver version was this on? Does the game run on a different browser on that machine?

I cannot reproduce on my Windows 10 laptop - the game runs fine.

The only webgl warning in the log is "texImage2D: Conversion requires y-flip.", which should not be fatal.
Flags: needinfo?(ithompson4)
Whiteboard: [testday-20170217] → [testday-20170217][gfx-noted]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(ithompson4)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.