This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 95557 - Memory leak behavior experienced when running ant task
Summary: Memory leak behavior experienced when running ant task
Status: CLOSED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: issues@performance
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2007-02-14 14:30 UTC by m_potociar
Modified: 2011-05-25 11:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description m_potociar 2007-02-14 14:30:54 UTC 
When I run an ant task to clean and build WSIT project (wsit.dev.java.net),
netbeans start to consume more and more memory and it never releases it back,
even after the task is finished. I have tried to even invoke GC manually with no
obvious improvement. IMHO this behaviour is not acceptable because it makes
development on a machine with 1GB RAM pretty impossible. The behaviour is not
experienced when executing ant directly from command line.

Sending some system data:

process tree (shell command: ptree):

  5442  /bin/sh /opt/netbeans-5.5.1dev/bin/netbeans --userdir /export/home/m_po
    5455  sh /opt/netbeans-5.5.1dev/bin/../platform6/lib/nbexec --jdkhome /usr/
      5496  /usr/jdk/instances/jdk1.5.0/bin/java -Djdk.home=/usr/jdk/instances/

memory allocation before ant is run (shell command: top -osize):

   PID USERNAME LWP PRI NICE  SIZE   RES STATE    TIME    CPU COMMAND
  5496 m_potoci  25  49    0  352M  158M sleep    0:13  0.09% java

memory allocation after ant is run (and finished) (shell command: top -osize):

   PID USERNAME LWP PRI NICE  SIZE   RES STATE    TIME    CPU COMMAND
  5496 m_potoci  20  49    0  681M  507M sleep    0:48  0.06% java

Most important parameter is RES, which reports amount of resident memory process
occupies.
Comment 1 Marian Mirilovic 2007-02-15 09:32:00 UTC 
We need to investigate, what object caused the leake - reassign to performance
team for investigation.
Comment 2 Petr Nejedly 2007-02-15 13:45:48 UTC 
I cannot reproduce the problem in dev builds.
I checked out the wsit/wsit project, opened the top level folder as NB project
and tried clean-build from the menu.
My RSS went from 300 to 350MB throughout the operation which is not that bad
given the fact that it was the very first thing I did after I restarted my IDE.
Note that 158MB of RSS is quite unrealistic figure for NB-dev.
I'll try this with 5.5.1 daily...
Comment 3 Petr Nejedly 2007-02-15 14:45:59 UTC 
I can't reproduce the problem in 5.5.1 (20070214) either.
Comment 4 m_potociar 2007-02-15 16:27:57 UTC 
Hi,I just installed latest build (200702150600) and I cannot reproduce the
behavior either. I would say that the bug can be closed. Thanks for your quick
response though.
Comment 5 Petr Nejedly 2007-02-15 16:40:41 UTC 
OK, closing.