-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Webgazer too slow #354
Comments
Would love if you could test it! |
I checked it with my resource monitor and task manager now, no sudden surges of memory consumption. And can also confirm my system is capable enough to run this script (i5-1240p, 16 GB of RAM, RTX 2050 with 4GB of VRAM). I tried testing the integration with vanilla JavaScript and it was fast enough. I expect the issue to be with something related to React and Webgazer. I am unable to use the npm method to import Webgazer so I'm using Script tag in HTML and using it in React JS using window.webgazer and useEffect hook. is there any issue with how I'm importing or any workarounds with using react? |
I found out the root cause of the problem. Local session storage was set to true, which messes up with the memory storage and stuff. The website runs better now but at the expense of recalibration every single time. |
Are you using localForage in WebGAzer, or localStorage? localForage should not have the typically low memory limit (5 mb) that localStorage has. How long does it take before it slows down? |
As the title suggests, webgazer was very fast at first but now it has slowed down a bit. Maybe theres something buggy in my react code but honestly the integration was really quirky. Is there a memory leak or is it just my system? I would appreciate someone confirming this issue.
The text was updated successfully, but these errors were encountered: