User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20150222232811 Steps to reproduce: Visit http://madebyevan.com/webgl-water/ Actual results: Firefox within 30 seconds maxed out its memory usage @ 3.5gb but did not crash. Expected results: The webgl demo should have worked correctly with out the browsers memory usage maxing out.
Created attachment 8570986 [details] Only affect firefox 36.0 on this profile. Seems to be a setting in this old profile. Does not happen in a clean profile or other Firefox versions.
I can reproduce the memory problem if HWA disabled.
Status: UNCONFIRMED → NEW
Component: Untriaged → Canvas: WebGL
Ever confirmed: true
Product: Firefox → Core
Yeah, I wasn't 100% sure
Summary: webgl menory leak [webgl water demo] → webgl memory leak [webgl water demo]
Finally got it to crash Current Firefox 37.0b1 https://crash-stats.mozilla.com/report/index/7b80a511-99ab-49e1-80cb-7f17e2150301 Can be produced on http://www.bongiovi.tw/experiments/webgl/blossom/ with H/W disabled Can be produced on http://dev.miaumiau.cat/sph/ with H/W disabled Locks up almost instant on http://www.spacegoo.com/wingsuit/# with H/W disabled Can be produced on http://playcanv.as/p/JtL2iqIH with H/W disabled Also the window detached from the window at one point see attached screenshot.
This bug is resolved in 36.0.1 This bug looks to be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1137251
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1137251
You need to log in before you can comment on or make changes to this bug.