🚀 go-pugleaf

There are some memory problems with JBuilder 3.5 (and 3.0 and 2.0 as well).
These are for a large part due to memory leaks in Swing and thus common to
all Swingbased applications. Performance will start to decrease after a few
hours of having the application loaded.
It is recommended to stop Swing applications every hour or two and restart
them afterwards to clear any memory that may have been lost.
This goes for even the smallest applications (once used a Java-based
text-editor that lost a megabyte a minute, taking maybe 2 MB itself).
Compared to that, JBuilder is good ;)
Using the most recent JDK also helps, the problems have gotten less with the
release of 1.2.2.

--
Jeroen T. Wenting
jwenting@hornet.demon.nl

"Francisco Gongora" <fgongora@marsys.com> wrote in message
news:39d3bd10$1_2@dnews...
> Hello Folks:
> I am developing a Java application with swing components with JBuilder 3.5
> on NT with 128MB, 2GB swapping virtual memory and enough HD space > 2HB.
> Although the application is not large ( menu, panels and a small table
> JTable); while editing, running and debugging I notice how JBuilder start
to
> act very slow.  It actually slow the whole machine, and in fact Task
> Manager' Mem Usage shows how "java.exe" which starts at about 10 MB raise
up
> to more than 100MB.  At this point, it is really difficult to keep
working.
> I tried memturbo.exe which someone subjected in the net.  At the beginning
> it seems to free mem. but them java.exe starts to grow as I said before.
Is
> it any remedy to this situation?  Is it natural for JB. to behave this
way?
> Any help will be appreciated.
> Regards
> Frank
>
>