large number of parallel tilesource requests make chrome throw net::ERR_INSUFFICIENT_RESOURCES
See original GitHub issueHi, I have more than 2000 iiif tiles, which have more than 2000 tilesource info.jsons, for example, ‘tileSource: /tiles/1/info.json
… tileSource: /tiles/2000/info.json
’. When calling viewer.open, it sends lots of parallel xhr requests to get info.json, some requests will cause Chrome throw net::ERR_INSUFFICIENT_RESOURCES.
Is there a way to fix this? Any settings in openseadragon or any other better ways of requesting tilesource when calling viewer.open? Thanks
Issue Analytics
- State:
- Created 9 months ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Issues · openseadragon/openseadragon - GitHub
large number of parallel tilesource requests make chrome throw net::ERR_INSUFFICIENT_RESOURCES ... AJAX concurrency limit option for tile source requests, ...
Read more >Chrome ERR_INSUFFICIENT_RESOURCES workaround
The error means your code is overloading your memory (most likely, or the quota of pending requests was exhausted).
Read more >Too many resource requests by renderer can cause memory ...
Once the constraint is reached, subsequent requests will fail with net::ERR_INSUFFICIENT_RESOURCES. The bound is defined as "25 MB", which ...
Read more >ERR_INSUFFICIENT_RESOUR...
I'm encounting a crash due to resource issues when previewing my game in Chrome. I have thousands of frames of images all up...
Read more >ERR_INSUFFICIENT_RESOUR...
ERR_INSUFFICIENT_RESOURCES error on making ajax calls ... I refresh the data of both tables every 3 seconds, using set interval
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Aiosa I think this issue isn’t really about requesting thousands of high-resolution files at once; it is loading thousands of light-weight
info.json
files that describe the zoomable images. If these could be handled appropriately (by batching, throttling the requests, or otherwise) then the viewer will take care of making the actual image requests for the high-resolution data in the normal, useful way.@LuckyLuo, @ChiliJohnson is that right?
@LuckyLuo It looks like @ChiliJohnson is indeed still working on #2242. Feel free to take a look at the code or try out the work in progress if you want to have any input on how it gets finished up 😃