build tested - 6u10 pit b13 from the following location
http://j2se.east/plugin/1.6.0_10-pit/2008-02-22.08_28/
OS tested - Nevada x86, XP Pro, RHEL 5
browsers tested - FF3,IE7

Description - java.lang.OutOfMemoryError is thrown with the new plugin under some scenarios.
In one particular scenario we are defining a byte array of around 55M and on refreshing the browser/reloading the applet java.lang.OutOfMemoryError will get thrown. If we set array to null inside the destroy method then java.lang.OutOfMemoryError is not getting thrown.

Steps to reproduce:

Run the following applet
http://sqeweb.sfbay/deployment2/jitu/plug-bug/ALC/MemoryTest.html

Reload the applet several times until the following exception is thrown:
Exception in thread "thread applet-MemoryTest-11" java.lang.OutOfMemoryError: Java heap space
at MemoryTest.init(MemoryTest.java:65)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
This may be a regression of 6613370.
It looks like the applet reference will still be bound and no GC will happen
when the browser initiates an applet stop/destroy.

We have to look into the 'destroy()' logic,
where we have a left over applet reference,
and therefor a memory leak.