As discussed, this is going to regress WebGL performance since we have to make a copy of the texture every frame. Jeff: Does this fit in at all with your double/triple buffering work at all? Would be nice if we could just swap the textures around instead of copying.
Comment on attachment 681160 [details] [diff] [review] Texture Sharing I'd like to see some performance measurement since we're doing a lot more work then what the optional buffer swapping implementation should be. I'm not convinced that we want to do this over reading back the pixels instead of just going directly to swap our back buffer texture.
(In reply to Jeff Gilbert [:jgilbert] from comment #3) > This functionality is provided in bug 716859. So this bug can be closed / marked as duplicate?
Fixed by bug 716859.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.