memory leak in 3.3?

[Jacob Gladish]

While trying to reproduce a problem I've been seeing in 3.1, I decided
to run my test program under 3.3 to see if this is something already
fixed and have noticed that the memory size has grow to be 825 megs over
the past 17 hours and appears to be continually growing. I searched the
bug database and there does not appear to be anything under memory leaks
for 3.3. Does anyone know of any cases where I might encounter this. The
code I'm running is attached. 


NOTE: The problem I've seen in 3.1 is that the program eventually throws
an IllegalMonitorStateException from _Jv_MonitorExit, with the message
"current thread not owner", and then deadlocks. I'm using hash
synchronization.


thanks
jake





-------------- next part --------------
A non-text attachment was scrubbed...
Name: DeadLockTest.java
Type: text/x-java
Size: 1263 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/java-patches/attachments/20031001/59295945/attachment.bin>