Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Is there a workaround to prevent a java applet from crashing firefox in severe memory shortage situations?

  • 1 Mbohovái
  • 1 oguereko ko apañuái
  • 1 Hecha
  • Mbohovái ipaháva guigs

pa-at-gad
pa-at-gad
more options

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.

Opaite Mbohovái (1)

guigs
guigs
more options

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