Thanks for feedback, confirms what I thought... I met the same issue with Google Native Client actually. In that case I ended up doing the image get in the C++ too, and rendering using the pp::Graphics2D API. When using pp::Graphics2D::ReplaceContents it seemed that the browser was smart about reusing buffers (as documented). Conceivably, moving these operations into the C++ might make more sense with emscripten too - I'm not sure what APIs are available to the C++. ben
-- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
