-
Notifications
You must be signed in to change notification settings - Fork 7
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
RangeError: Array buffer allocation failed #93
Comments
Limit appears to be even lower for larger types. On Chromium:
So we're still at about a 2GB allocation limit (4 bytes per entry). |
Additional debugging. I can consume more memory if I break it into smaller allocations:
|
Any progress on this? It rather severely limits the maximum size of the data that you can have in the database if you're running in a browser (like in ssb-browser-demo). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running into an issue in ssb-browser-demo which seems to be stemming from this line:
https://github.com/ssb-ngi-pointer/jitdb/blob/c143df20db1f08a74f1a7cf54bb9c7058a394865/index.js#L186
(See the initial report at arj03/ssb-browser-demo#90 )
My system's nowhere near 100% RAM consumption, so I did a bit of experimenting. On Firefox I get the following results:
So there's a rough 2GB limit (<2GiB). If I do the same on Chromium:
Pretty similar results.
The text was updated successfully, but these errors were encountered: