Skip to content
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

Use virtual image loading #342

Open
ivmartel opened this issue May 17, 2017 · 0 comments
Open

Use virtual image loading #342

ivmartel opened this issue May 17, 2017 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@ivmartel
Copy link
Owner

(not sure about the name...)
When loading a large number of images (either individually or in a multi-frame dataset), the viewer can reach the maximum allowed memory allocation of the browser. In Google Chrome this will result in the "Aw, snap" or "He's dead Jim!" out of memory error.
One solution could be to only load the images that are needed for visualisation and cache the others. For ideas, see the answers to this SO question: how-do-you-detect-memory-limits-in-javascript.

Originated from #255, relates to #249.

P.S. It seems 64bits versions of browsers are allowed more memory. I would recommend updating your browser if you are using the 32bits version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant