I just tried an experiment. I don't need to do any debugging in
NetBeans. I actually don't need to do anything at all! If I run
NetBeans and it has a project opened (the last project I was working
on, I don't explicitly load the project), I can see the java process
that is NetBeans consume memory at a rate of just under a megabyte a
second (using 'top' in a Terminal window). The memory toolbar in
NetBeans does not reflect this memory usage. After a several minutes
the VMSIZE as reported by 'top' increases to over a GB and the system
response grinds to a stand still.
So the problem with a bug report is that the only step is "launch
NetBeans", and obviously that doesn't seem to be enough.
If you have any ideas that would help provide a more useful bug
report please let me know.
My system did have various DPs of Java 5 installed and i installed
the latest release version over top of them, but I can't say that it
related to this issue or not. I have no reason to believe that my
Java install is corrupt. I also have the latest Java 6 DP installed,
but I don't use it.
$ java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
Scott
On 10-Jul-06, at 2:37 AM, mkleint wrote:
please file those issues at http://www.netbeans.org/community/
issues.html
I'm doing my development on macosx (PowerPC G5 with 1 gig of ram)
and I keep netbeans running for a week, never experiencing any
problems. (with default jvm settings). I don't much debugging though..
please include steps to reproduce or at least the features you use
frequently so that the source of memory leaking can be identified.
Milos Kleint
Scott Palmer wrote:
On 8-Jul-06, at 4:42 AM, Fabrizio Giudici wrote:
On Jul 7, 2006, at 15:12 , Scott Palmer wrote:
On 6-Jul-06, at 9:05 AM, Marc Gracia Galobart wrote:
I'm more than happy with Netbeans.
Due to massive memory leaks when running NetBeans on Mac, I can
only use it for 30 mins max before I need to shut it down to
reclaim RAM. It may be related to how many times I invoke the
debugger.
Am I the only one seeing this?
I have never been forced to shut it down, even if it has more
problems with memory than Eclipse (I've to add that i mostly use
NetBeans5.5beta, maybe there's some fix in it).
Well NB 5.5 has worse problems... the display is often corrupted
such that the source code is not painted and various images
appear in the wrong place. It's much less stable on my system.
I only have 768MB in this PowerBook. Which should be enough to
run NetBeans for small projects.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
