Out of Memory issue
Answered
We just started working with Studio Web and when previewing, or when deployed, the browser keeps running out of memory when doing simple tasks such as zooming/panning. We have a rather large webmap, but it's not a problem when used in AGO's web viewer. Has anyone else found this issue? It's going to be a serious issue for us if we cannot include these map services in our web map within the Studio Web application.
-
Hi Erik
Are you running a 32 bit browser? If so that will cause out of error issues by doing almost anything.
Thanks
Rohan
1 -
Yes, we are operating in 32bit. However, Chrome is managed by our organization and is 32bit by default.
Perhaps advocating for 64bit browsing capabilities is a solution, but it seems like a bandaid. Not all users will have 64bit browsing capabilities. If they aren't able to leverage our application unless they are on 64bit, that leaves a bit of a functionality gap. If there are ways to manage bloat in Studio Web, I'd like to entertain them.0 -
Hi Erik
In the requirements section for Vertigis studio web, a 64 bit browser is required (see here).
I'm not sure what you can do if this is an organisational requirement, edge by default will be install in 64 bits on a 64 bit machine so you could try using that?
Thanks
Rohan
2 -
Thanks Rohan!
0 -
Nice catch Rohan Christopherson! Yes, as mentioned in our docs we require a 64-bit browser. The amount of memory used in most web-based applications nowadays necessitates a 64-bit browser.
A 32-bit address space limits you to 4GB of RAM, whereas with a 64-bit address space the maximum is ~18.4ExB (that's exabytes!). Erik Engstrom, I'd encourage your IT team to update their deployment package to a 64-bit browser.
1
Please sign in to leave a comment.
Comments
5 comments