Keisha Posted September 21, 2018 Share Posted September 21, 2018 I am seeing these errors in my chrome browser after updating to Phaser v3.13.0. Anyone please tell me what are these errors and how to solve them. Phaser v3.13.0 (WebGL | Web Audio) https://phaser.io 256 WebGL: INVALID_OPERATION: bindTexture: attempt to bind a deleted texture phaser.min.js:1 WebGL: too many errors, no more errors will be reported to the console for this context. setTexture2D @ phaser.min.js:1 setTexture2D @ phaser.min.js:1 batchSprite @ phaser.min.js:1 t.exports @ phaser.min.js:1 render @ phaser.min.js:1 render @ phaser.min.js:1 render @ phaser.min.js:1 render @ phaser.min.js:1 step @ phaser.min.js:1 step @ phaser.min.js:1 e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 requestAnimationFrame (async) e @ phaser.min.js:1 Link to comment Share on other sites More sharing options...
rich Posted September 21, 2018 Share Posted September 21, 2018 With what code? As none of the examples exhibit it that I've seen. Link to comment Share on other sites More sharing options...
Keisha Posted September 25, 2018 Author Share Posted September 25, 2018 On 9/21/2018 at 5:24 PM, rich said: With what code? As none of the examples exhibit it that I've seen. Never mind. This error had occurred because of my wrong code. Sorry Link to comment Share on other sites More sharing options...
cornstipated Posted September 26, 2018 Share Posted September 26, 2018 there seems to actually be a bug mr davey use graphics and do a generate texture and destroy. The texture gets destroyed in 3.13 Link to comment Share on other sites More sharing options...
rich Posted September 26, 2018 Share Posted September 26, 2018 Yes, there's a bug in generateTextue as confirmed in GitHub issues: https://github.com/photonstorm/phaser/issues/4050 But, as I said above, unless someone actually posts the code that causes their error (like the OP of this thread) then it's impossible to know if it's related or how to fix it. Link to comment Share on other sites More sharing options...
Keisha Posted September 27, 2018 Author Share Posted September 27, 2018 13 hours ago, rich said: Yes, there's a bug in generateTextue as confirmed in GitHub issues: https://github.com/photonstorm/phaser/issues/4050 But, as I said above, unless someone actually posts the code that causes their error (like the OP of this thread) then it's impossible to know if it's related or how to fix it. Yes. I was using the generateTexture() method for creating textures from the graphics and later i removed it and loaded different textures from png`s when i started getting the errors. I didn't know why i was getting those errors. Link to comment Share on other sites More sharing options...
rich Posted September 27, 2018 Share Posted September 27, 2018 Yeah it’s an annoying bug and will be fixed in the next few days. My comment above was directed at @cornstipated really, not you. Link to comment Share on other sites More sharing options...
Keisha Posted September 27, 2018 Author Share Posted September 27, 2018 37 minutes ago, rich said: Yeah it’s an annoying bug and will be fixed in the next few days. My comment above was directed at @cornstipated really, not you. Yes I got it. Please look into this?: Link to comment Share on other sites More sharing options...
Recommended Posts