You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there
I am using noVNC within my organization. Randomly, some users encounter the 'ns_ERROR_OUT_OF_MEMORY' error
I have investigated this error and have a hypothesis related to the method that retrieves data entirely. I believe this method should be optimized to fetch data in chunks instead of retrieving the entire dataset at once
at line 201 display.js in core modules
saveImg = this._drawCtx.getImageData(0, 0, canvas.width, canvas.height);
OS: ubuntu and windows
Browser: firefox
Browser version: 132
noVNC version: 1.3
The text was updated successfully, but these errors were encountered:
Unfortunately, the memory needs to be allocated somewhere during this stage. Getting it in smaller chunks would just mean more of them. The only hope would be if other types of memory has a different limit (e.g. another canvas).
Are your users using a very large screen resolution? It would be very helpful if we can reproduce this so we can try different approaches.
Getting it in smaller chunks would just mean more of them
Why you say that getting in smaller chunks consume more memory?
Instead i load all the data once into memory i load it chunk by chunk into memory.
Are your users using a very large screen resolution
different users have different resolutions and i cant tell you exact resolution that problem happens.
Also i open vnc.html in an iframe in my application, does it matter?
Hi there
I am using noVNC within my organization. Randomly, some users encounter the 'ns_ERROR_OUT_OF_MEMORY' error
I have investigated this error and have a hypothesis related to the method that retrieves data entirely. I believe this method should be optimized to fetch data in chunks instead of retrieving the entire dataset at once
at line 201 display.js in core modules
saveImg = this._drawCtx.getImageData(0, 0, canvas.width, canvas.height);
The text was updated successfully, but these errors were encountered: