-
Notifications
You must be signed in to change notification settings - Fork 354
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
Out of memory #72
Comments
…clude a test for characters outside of basic ASCII. This addresses #72.
As of 1.5.0, Viz.js doesn't try to reuse the memory allocated on its initial run. This is an attempt to address situations like #65 and #59, but admittedly using kind of a blunt instrument. What browser are you seeing this in? How many graphs are you generating in a row? Are they generated inside a Both techniques I've used in the memory test appear to work in the browsers I've had a chance to test so far: https://github.com/mdaines/viz.js/blob/524f7f84cdb392f1b72e9981fdfe1dc3b71124c6/tests/memory.js |
Thank you for the quick reaction! I'm using Firefox 47.0.2 on Windows. The graphs are not created in a loop but manually when browsing through the app's sentences (it's an app for linguistically annotated text). The memory exception occurs after rendering about 60 graphs. An example graph:
|
I was able to get Firefox 47 on Windows to throw an out of memory error using the attached test case at about ~200 calls for that graph (see console for counts). However, Firefox 50 passes that test (1000 calls). |
I'm very sorry for the late response – I've been too busy with other stuff... The memory issue seems to be quite system-dependent. When testing with Firefox 47 on Windows, 32bit, 3GB RAM, the error occured after 70 graphs. I also checked with FF 51 on Linux (same hardware) – there the error occured after generating 60 graphs (though, surprisingly, it ran up to 550 once). I also tested v1.7.0 with totalMemory set to 32MB, which didn't throw the error (32 was the highest value possible). Next I'll test the new version on my app... |
Sorry for not having given you feedback on this one... I haven’t encountered any more problems now, so I think this issue can be closed. |
Using one of the v1.5.0 builds, I get an
uncaught exception: out of memory
when generating a number of graphs in a row.The text was updated successfully, but these errors were encountered: