This is the shadowing CR for https://bug.oraclecorp.com/pls/bug/webbug_print.show?c_rptno=14080741
If applet with legacy_lifecycle=true trigger agressive heap memory allocation to a level close to max memory value (eventhough the actual memory usage is still low), and user navigate away from the page containing the applet, the applet will be destroyed prematurely.
- Make sure java console is show and tracing is set at top level (5/all).
(ignore the third applet class not found error)
- Click on buttons until total mem value is close or equal to max mem value.
- Move away from the page to trigger applet stop call. Will see on the console applet is destroy.
Expect: applet not destroyed and not reloaded but reused from legacy lifecycle applet cache.
Test case files: