Open
Bug 1386313
Opened 7 years ago
Updated 2 years ago
[Try build] Jenga WebGL cannot be played if the webpage is refreshed 3-4 times
Categories
(Core :: Graphics: CanvasWebGL, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox55 | --- | wontfix |
firefox56 | --- | wontfix |
firefox57 | --- | fix-optional |
People
(Reporter: VladB, Unassigned)
Details
(Whiteboard: [gfx-noted])
User Agent: Mozilla/5.0 (Windows NT 10.0; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170801011416 System: Windows 10 x86, 3GB of RAM [Notes]: - This issue is only reproducible on the Firefox beta try build 20170801011416 - This issue is not reproducible on latest Nightly. [Steps]: 1. Open try build browser and open a new tab. 2. Go to http://chandlerprall.github.io/Physijs/examples/jenga.html. 3. play the game and Refresh the page after it ended. 4. Repeat this 3-4 times [Expected results]: - The game can be played without issues. [Actual results]: - After 3-4 page refreshes the game cannot be played anymore and the browser becomes sluggish. [Additional Notes]: - In the browser console there is the following error: THREE.WebGLRenderer 60 three.min.js:416 uncaught exception: out of memory (unknown) Performance profile: https://perfht.ml/2tZITq0 . Maybe it will be of help.
Updated•7 years ago
|
Summary: [Try build] Jenga WebGL cannot be played after if the webpage is refreshed 3-4 times → [Try build] Jenga WebGL cannot be played if the webpage is refreshed 3-4 times
Comment 1•7 years ago
|
||
Can you please see if the below two builds reproduce as well? These are "real" 56 Beta builds now that Gecko 56 has been merged from m-c to beta. Win32: https://queue.taskcluster.net/v1/task/Wf0khHJvRcK0FTJu_IgyEQ/runs/0/artifacts/public/build/target.zip Win64: https://queue.taskcluster.net/v1/task/Jnoy1CaYSXa7E5yGwjXxmg/runs/0/artifacts/public/build/target.zip
Flags: needinfo?(vlad.bacia)
Reporter | ||
Comment 2•7 years ago
|
||
I can confirm that the issue is reproducible with both builds from comment 2.
Flags: needinfo?(vlad.bacia) → needinfo?(ryanvm)
Comment 3•7 years ago
|
||
I wonder if this is related to the CI issues affecting Beta at the moment.
Flags: needinfo?(ryanvm) → needinfo?(jgilbert)
Are these CI issues resolved now?
status-firefox55:
--- → wontfix
status-firefox56:
--- → wontfix
status-firefox57:
--- → fix-optional
Flags: needinfo?(jgilbert) → needinfo?(ryanvm)
Priority: -- → P3
Whiteboard: [gfx-noted]
Comment 5•7 years ago
|
||
Yes, the issues in comment 3 were referencing the problems that were solved by turning off async pref saving.
Flags: needinfo?(ryanvm)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•