I am also seeing memory problems with JDK1.2 pre2. I am running RedHat 5.2,
glibc 2.0, and was not seeing this behaviour with jdk1.2pre1. I have also
tried RedHat 6.0 under VMWare under Redhat 5.2 and the GlibC 2.1 version has
the same behaviour.
If you are interested to see if it behaves the same on your system, try out
the test program:
http://www.nsdev.org/test2d.jar
By running it:
java -jar test2d.jar
On my system, if I drag the nodes around on the screen, the memory will
eventually be exhausted, or there will be a deadlock. There are also other
bugs with the 2d system that can be shown by dragging the node closest to the
bottom of the screen from side to side... I'd be interested if that happens on
anyone else's system. It doesn't happen in Windows, or on Solaris jdk1.2
ports.
Under RedHat 5.2, with XFree86 3.3.3.1 when dragging I sometimes get black
blocks appearing on the screen near diagonal antialiased lines. Surprisingly
this does not happen under my RedHat 6.0 installed under VMWare, go figure.
The program does exhibit the memory leak and deadlocking under both setups
though. Like I mentioned, this memory leak does not happen under jdk1.2pre1.
If you want to play, hold down the control key, and start putting more nodes
on the screen by left clicking the mouse... then drag between the nodes to
make more links. The more links, the faster the memory goes away. :I
Diva is found at: http://ptolemy.eecs.berkeley.edu/diva/index.html
Cheers.
-Neal
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
