-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[browser][crypto] Fix Quota Exceeded error #48692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[browser][crypto] Fix Quota Exceeded error #48692
Conversation
|
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsAdd batched implementation to fix error with quota exceeded limit.
Add and/or update tests for exceeding the quota limit of browser set at 65536. The tests only went up to 65536 so this error was never caught. Fix #48584
|
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsAdd batched implementation to fix error with quota exceeded limit.
Add and/or update tests for exceeding the quota limit of browser set at 65536. The tests only went up to 65536 so this error was never caught. Fix #48584
|
|
Is there a specific reason why we aren't just writing directly into the wasm heap using views, instead of using these scratch work arrays? |
|
Do you mean this one: var wrkArray = new Uint8Array(Module.HEAPU8.buffer, buffer, bufferLength); That does write into wasm heap. |
I don't think you need wrkArray, you should be able to create small views into the wasm heap and then use |
|
ok |
|
updated to use suggested code from katelyn |
|
Doesn't line 13 have the potential to integer overflow? |
It's not an integer, so no. JS can represent integral numbers up to 53 bits in size |
Add batched implementation to fix error with quota exceeded limit.
Add and/or update tests for exceeding the quota limit of browser set at 65536.
The tests only went up to
65536so this error was never caught.A small repo from issue:
1024 * 1024 = 1048576
Fix #48584