Is there a workaround to prevent a java applet from crashing firefox in severe memory shortage situations?
In our large banking application, java applets crash firefox in severe memory shortage situations.
We suspect the java plugin NOT to check the malloc result which is null.
As a workaround, we have the idea to test memory availability in advance such that we at least may prevent firefox from crashing by refusing to load the applets.
But how much memory does the java plugin allocate and how many chunks will be needed?
We are going to explore stackdumps to find out but suggestions are much appreciated.
In our large banking application, java applets crash firefox in severe memory shortage situations.
We suspect the java plugin NOT to check the malloc result which is null.
As a workaround, we have the idea to test memory availability in advance such that we at least may prevent firefox from crashing by refusing to load the applets.
But how much memory does the java plugin allocate and how many chunks will be needed?
We are going to explore stackdumps to find out but suggestions are much appreciated.
모든 댓글 (1)
Monitoring usage of memory in firefox is about:memory. Click measure and it will give you an estimate of each page memory consumption.
This tool is helpful too: Profiler