Created attachment 637286 [details]
I found this while running the WebGL Conformance Tests in a debug build of trunk. If you visit the attached webpage and then visit about:memory, Firefox will always NS_ABORT() when getting the memory usage of unintialized render buffers. This is because it doesn't handle the case where mInternalFormatForGL is null.
Created attachment 637303 [details] [diff] [review]
Here's a patch that handles the null case for render buffers and textures.
Try server run: https://tbpl.mozilla.org/?tree=Try&rev=09132969a207
Opening the test case and about:memory in today's Nightly does not cause a crash now.