Issue metadata
Sign in to add a comment
|
Copying canvas to webgl texture cause memory leak and webGL_CONTEXT_LOST
Reported by
david.ca...@gmail.com,
Sep 7
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. Go to https://playground.babylonjs.com/#Y6XVXY#5 2. Click multiple time in the green canvas 3. See memory increase until context lost What is the expected behavior? not crashing What went wrong? We think that there is a memory leak when updating webgl texture with the canvas Did this work before? Yes Chrome 68 Does this work in other browsers? N/A Chrome version: 69.0.3497.81 Channel: stable OS Version: 10.0 Flash Version: Thanks!
,
Sep 9
,
Sep 10
david.catuhe@ Thans for the issue... Unable to reproduce this issue on reported chrome 69.0.3497.81 Using Windows 10.Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome 2. Navigated to given URL " https://playground.babylonjs.com/#Y6XVXY#5 " 3. Clicked multiple time on the green canvas As we have not seen any crashes and memory high @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here and requesting you to provide chrome crash id from chrome://crashes. Thanks.!
,
Sep 11
I confirm that you did not miss anything. And I cannot repro anymore.. Really sorry for the false alert :(
,
Sep 11
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 12
Thanks for the update... As per comment #4, closing this issue as Won't fix.Removing Needs-Bisect label to it. @Reporter: Please feel free to raise a new issue if issue is still seen on chrome. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by david.ca...@gmail.com
, Sep 7