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 94280 - Memory leaks in Visual Web Pack
Summary: Memory leaks in Visual Web Pack
Status: RESOLVED DUPLICATE of bug 105078
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords: PERFORMANCE
Depends on: 99299 99308 100268 100270
Blocks:
  Show dependency tree
 
Reported: 2007-02-03 16:38 UTC by Roman Strobl
Modified: 2007-05-29 23:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2007-02-03 16:38:24 UTC
I have a suspicion that Visual Web Pack has serious memory leaks. Whenever I
work with visual web pack it ends up eating all available memory, no matter how
much memory I allocate using -J-Xmx parameter. The default settings of 256 MB on
heap is not enough even for basic web applications - I was able to get out of
memory by creating one form with simple data providers. When I close the web
project, objects in the memory don't get released and thus the user has to
restart the IDE after several hours of working with visual web pack. Please
investigate. Also reported by customers.
Comment 1 Jayashri Visvanathan 2007-02-16 19:36:42 UTC
Test case would be very useful for further investigation.
Comment 2 Roman Strobl 2007-02-16 21:17:15 UTC
Here is a test case:

1. Start NetBeans IDE + Visual web pack and measure memory usage. In my case it
is 17.7 MB after start (after GC).
2. Create new Visual Web Application.
3. Drag & drop 10 checkboxes to the page.
4. Save the project and close it.
5. Invoke GC and measure available memory. It will be more than 40 MB, although
it should go back to 17.7 or at least similar.
6. Repeat the steps above with new projects - try to use various components. The
memory will keep increasing. If you want to see bigger increase of memory, use
data-aware components and databinding.

This way it is possible to get the IDE into the state when no memory is left due
to objects allocated in already closed projects. The issues get more serious if
the user opens more complex projects (this is just a small example).

Another way to reproduce this issue is to use Visual Web Pack for a couple of
days without IDE restart to build real applications. 

Adding David on CC., David, please add your comments.
Comment 3 David Botterill 2007-02-17 05:29:53 UTC
With the project I attached to 95012
(http://www.netbeans.org/nonav/issues/showattachment.cgi/38633/pluginportal.zip)
you can see the memory climb very fast while working in two specific areas, the
outline and the CSS Editor.  While in here you'll see the memory used jump from
around 150MB to well over 550MB at times.  If I force GC, I do see a big
reclamation of memory.  However, the memory usage does steadily climb until the
point where I have to shut down the IDE and restart.
Comment 4 Quy Nguyen 2007-05-29 23:37:57 UTC

*** This issue has been marked as a duplicate of 105078 ***