Three.js - textures are not tied to unit 0 Error

Question

With today's Chrome update (version 50.0.2661.86 (64-bit) OSX), my tr.js-based application started to display this warning:

[.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 0

and the application no longer downloads (it just got stuck on the download screen).

To give a context of the strangeness of this error, we create grids with a texture + normal map, and there is a strange behavior when: - if we load all instances of the application, - if we load less instances, applications load

For information, we load all the textures in the material callback, so the previous Stackoverflow answers that provide solutions to this problem really don't work.

Does anyone have an idea of ​​what we can change to make this work? Or should we open a ticket to the Chromium team reporting the problem?

It worked great until today's update.

Answer 1

If you add:

 this.image = image; // retain a reference to the object to prevent garbage collection 

after line 18419 of three.js (r76), it will also fix loading TextureLoader in the latest version of Chrome.