FULL PRODUCT VERSION :
Java Plug-in 1.5.0_14 using JRE version 1.5.0_14 Java HotSpot(TM) Client VM and Java Access Bridge for Windows OS

ADDITIONAL OS VERSION INFORMATION :
Windows XP

EXTRA RELEVANT SYSTEM CONFIGURATION :
Java Plug-in 1.5.0_14 using JRE version 1.5.0_14 Java HotSpot(TM) Client VM and Java Access Bridge for Windows OS

A DESCRIPTION OF THE PROBLEM :
We are currently having a memory leak issue with Java Plug-in 1.5.0_14 using JRE version 1.5.0_14 Java HotSpot(TM) Client VM and Java Access Bridge for Windows OS. This leak happens through the following step by step process. One, we open up a new page containing a java applet. Second, we use the Java Access Bridge for Windows to retrieve information contained in the java applet for basic screen scraping purposes. Then the page containing the java applet is closed. Then the java applet page is opened again and screen scraped through the java access bridge. By repeatedly doing these steps we were able to render the applet unresponsive and received the following error in the Java Console.

Exception in thread "AWT-EventQueue-30" java.lang.OutOfMemoryError: Java heap space

Although through repeated testing the number associated with the AWT-EventQueue may change. We were able to replicate our finding through the use of the Java Ferret. The following options were enabled in the java ferret: Update from Mouse, Track Mouse Events, and Track Visible Data Property Events. By using these options it seems the garbage collector is unable to collect all the necessary objects and will ultimate run out of space to allocate new objects on the heap. Any help regarding this issue would be greatly appreciated. Please contact me directly if any further information is need

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
We are currently having a memory leak issue with Java Plug-in 1.5.0_14 using JRE version 1.5.0_14 Java HotSpot(TM) Client VM and Java Access Bridge for Windows OS. This leak happens through the following step by step process. One, we open up a new page containing a java applet. Second, we use the Java Access Bridge for Windows to retrieve information contained in the java applet for basic screen scraping purposes. Then the page containing the java applet is closed. Then the java applet page is opened again and screen scraped through the java access bridge. By repeatedly doing these steps we were able to render the applet unresponsive and received the following error in the Java Console.

Exception in thread "AWT-EventQueue-30" java.lang.OutOfMemoryError: Java heap space

Although through repeated testing the number associated with the AWT-EventQueue may change. We were able to replicate our finding through the use of the Java Ferret. The following options were enabled in the java ferret: Update from Mouse, Track Mouse Events, and Track Visible Data Property Events. By using these options it seems the garbage collector is unable to collect all the necessary objects and will ultimate run out of space to allocate new objects on the heap. Any help regarding this issue would be greatly appreciated. Please contact me directly if any further information is need

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Memory leak should not happen
ACTUAL -
Receiving
Exception in thread "AWT-EventQueue-30" java.lang.OutOfMemoryError: Java heap space

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Exception in thread "AWT-EventQueue-30" java.lang.OutOfMemoryError: Java heap space

REPRODUCIBILITY :
This bug can be reproduced always.