title: Three.js - there is no texture bound to the unit 0 Error
body: <p>Since today's Chrome update (Version 50.0.2661.86 (64-bit) OSX), my three.js based application started outputting this warning : </p>
  
  <p><strong><code>[.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 0</code></strong></p>
  
  <p>and the application is not loading anymore (it's just stuck in the loading screen). </p>
  
  <p>To give a context of the strangeness of this error, we are instancing meshes with a texture + normal map, and there is a weird behaviour where : 
  - if we load all the instances the application crashes
  - if we load fewer instances, the applications loads</p>
  
  <p>For info, we load all the textures in the material creation callback, so the previous Stackoverflow answers giving solutions about this issue don't really work. </p>
  
  <p>Does anyone have any idea of what we could change to make this work ? Or should we open a ticket to the Chromium team reporting an issue ? </p>
  
  <p>It was working perfectly before today's update.</p>