Enabling webgl-enable-ahardwarebuffer and loading a page with webgl content results in [this](https://searchfox.org/mozilla-central/rev/38652b98c6dd3bf42403eeb8c5305902b9a6e938/gfx/layers/ipc/CompositableTransactionParent.cpp#90) assertion failure in debug builds. `AsAndroidHardwareBufferTextureHost()` returns `nullptr` because the texture host is actually a `WebRenderTextureHost` wrapping a `AndroidHardwareBufferTextureHost`. In release builds the page appears to render correctly, though perhaps synchronization doesn't work correctly since this is to do with fencing? This occurs both with the GPU process enabled or disabled (after fixing bug 1754766). Sotaro, do you know how we should fix this?
Bug 1754820 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Enabling `webgl-enable-ahardwarebuffer` and loading a page with webgl content results in [this](https://searchfox.org/mozilla-central/rev/38652b98c6dd3bf42403eeb8c5305902b9a6e938/gfx/layers/ipc/CompositableTransactionParent.cpp#90) assertion failure in debug builds. `AsAndroidHardwareBufferTextureHost()` returns `nullptr` because the texture host is actually a `WebRenderTextureHost` wrapping a `AndroidHardwareBufferTextureHost`. In release builds the page appears to render correctly, though perhaps synchronization doesn't work correctly since this is to do with fencing? This occurs both with the GPU process enabled or disabled (after fixing bug 1754766). Sotaro, do you know how we should fix this?