Hamsters.js: [FireFox] Getting out of memory error
- What version of the library are you using?
latest version of library
- What operating system are you seeing the issue on?
windows 7
- Which platform (and or) browser are you seeing the issue on?
Core JS (Vanilla)
- What is the version of the platform (and or) browser you are seeing the issue on?
Am on Firefox browser , using core js with html5 canvas doing some heavy image processing so i mostly use hamster.js to split the image portion for processing between threads , recently i have started getting error out of memory and object could not be cloned , so i was wondering how overcome this memory issue , also any idea to allocate more memory in browser to JS so that out of memory issue not occur as i have 16GB RAM
Error Hamster #0: Line 0 in : uncaught exception: out of memory hamsters.js:607:5
onerror /js/vendor/hamsters/hamsters.js:607:5
uncaught exception: out of memory
Error Hamster #0: Line 0 in : DataCloneError: The object could not be cloned. hamsters.js:607:5
onerror /js/vendor/hamsters/hamsters.js:607:5
DataCloneError: The object could not be cloned.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (8 by maintainers)
@darkworks I am closing this ticket as you emailed and said v4.2.1 has resolved the out of memory issues.
Thanks for using the library.
@darkworks Give this release a try using persistence mode and report back to me, thanks!
https://github.com/austinksmith/Hamsters.js/releases/tag/v4.2.1
ok on weekend when free i will prepare demo link for you to check .
@darkworks I am reopening this issue as it concerns me a little that persistence mode has the memory issue but non persistence mode does not. If you could send me a demo link so I can investigate and fix persistence mode I would really appreciate that. Email it to me if you are uncomfortable with it being posted here, thanks!
ok thanks i fixed it by turning off persistence mode
Thanks for the bug report @darkworks unfortunately without being able to validate against your use case it is next to impossible for me to diagnose any memory related issues. If you are able to send me a demo link or access to the repo I could take a deeper dive into it and track down where exactly your memory issue is coming into play. Email that to me austin@asmithdev.com and it shouldn’t take long to figure out where the problem is. Thanks.