WebGL2RenderingContext.bufferSubData: Argument 3 can't be an ArrayBuffer or an ArrayBufferView larger than 2 GB
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
People
(Reporter: mehmet.soyturk, Unassigned)
Details
Attachments
(1 file)
1.11 KB,
application/x-zip-compressed
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/116.0
Steps to reproduce:
Opened the attached webgl.html
file in Firefox and clicked on the "start" button
Actual results:
Output from Firefox 116.0.3 (64-bit):
Mem allocated of 4096 MB
First bufferSubData call succeeded.
Uncaught TypeError: WebGL2RenderingContext.bufferSubData: Argument 3 can't be an ArrayBuffer or an ArrayBufferView larger than 2 GB
Expected results:
This is the output from Chrome 116.0.5845.111 (64-bit):
Mem allocated of 4096 MB
First bufferSubData call succeeded.
Second bufferSubData call succeeded.
More information: we develop a memory-hungry Unity application for the Web (C#), which uses Emscripten to generate Wasm code. Until recently, Wasm memory was limited to 2GB. We now see that 4Gb is supported on modern browsers (Chrome, Firefox, Edge, etc).
The application works fine on Chrome when we increase Wasm memory to 4 GB. However, it throws the error above when executed in Firefox.
This seems to be relevant: https://github.com/emscripten-core/emscripten/issues/17539#issuecomment-1242750815
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: CanvasWebGL' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
Can confirm this behaviour. Can repro on a build from Jan2019.
Chrome shows the expected messages.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Description
•