After updating Chrome to Version 50.0.2661.86 (64-bit) on OSX today, a warning started appearing in my three.js based application:
[.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 0
Due to this warning, my application is now stuck in the loading screen and not progressing further.
This issue becomes even more peculiar when considering that we are creating instances of meshes with textures and normal maps. Strangely enough: - the application crashes if we load all instances - but successfully loads when fewer instances are loaded
It's worth mentioning that we load all the textures in the material creation callback, so commonly suggested solutions from Stackoverflow are not effective in this case.
Does anyone have any suggestions on how to fix this problem? Or should we consider reaching out to the Chromium team to report this as an issue?
Prior to this update, everything was functioning perfectly fine.