GL textures display checkerboard placeholders of varying duration

I initially reproduced this issue on Slack as follows:

https://gist.github.com/oldschooljarvis/2011f7d9ea0586c1f059
Just `famous init` a new project and replace `src/index.js` with the above ^


The sequence of events is:

`(0ms)` First node is spawned containing a DOMElement utilizing the default logo image.
`(4000ms)` Second node is spawned with a Mesh instead, using the same default logo image but mapped as a GL texture. There is visible checkerboarding on load.
`(8000ms)` Third node is spawned, identical to the second, but does not checkerboard. Ditto all subsequent nodes.

The checkerboarding only manifests itself if it's a fresh page load. It will not manifest upon refreshing the page.
##

Then I created a second reproduction:

https://gist.github.com/oldschooljarvis/031463a0f8cb8fbf3d84
http://i.imgur.com/be3bldF.png/famous_logo_magenta.png (second image)


Similar setup, except we eschew the DOM node and deal purely in GL.

Sequence of events is:

`(1000ms)` Spawn node w/ default logo. - Bad checkerboxing, lasts nearly a second.
`(2000ms)` Spawn node w/ default logo again. - Zero checkerboarding.
`(5000ms)` Spawn node w/ modified logo image. - Slight checkerboarding, maybe a couple of frames. **Note: The .gif fails to capture this at all. (.gif limitation)**
`(6000ms)` Spawn node w/ modified logo image. - Zero checkerboarding.

However, if we refresh the page, checkerboarding is eliminated entirely:

##

The first reproduction demonstrated that the issue isn't related to normal browser image caching.

The second reproduction demonstrated that loading a new GL texture incurs only minor checkerboarding; that subsequent nodes of the same texture don't have the issue, and that the first texture in a scene is always afflicted with the worst checkerboarding. Perhaps the latter behavior is something to do with initialization of the texture system itself? No idea.

These issues were reproduced on Chrome Version 43.0.2357.124 m (64-bit), Windows 8.1. The system I tested on is a 3.8GHz i7 w/ an R9 270. Firefox and IE both exhibit the issue roughly the same. Chrome seems to be the worst for this issue, if only by a small margin.