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 125058 - memory leak in org.netbeans.modules.visualweb.jsfsupport.container.RaveFacesContext
Summary: memory leak in org.netbeans.modules.visualweb.jsfsupport.container.RaveFacesC...
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Winston Prakash
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 123530
  Show dependency tree
 
Reported: 2008-01-10 19:52 UTC by Quy Nguyen
Modified: 2008-02-04 15:18 UTC (History)
0 users

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 Quy Nguyen 2008-01-10 19:52:03 UTC 
The RaveFacesContext instance is not released from memory after a visual web project is closed.  This causes a
significant amount of model objects to leak in memory.

To reproduce:
1) Create a vw project
2) Close the navigator (suppresses another leak)
3) DnD some components onto the page
4) Close the page and the project
5) Open/close the properties window (suppresses another leak)

Many of the visualweb model objects are still in memory, held by the RaveFacesContext instance.
Comment 1 Quy Nguyen 2008-01-11 01:09:31 UTC 
Fixed.

Checking in FacesContainer.java;
/cvs/visualweb/jsfsupport/src/org/netbeans/modules/visualweb/jsfsupport/container/FacesContainer.java,v  <-- 
FacesContainer.java
new revision: 1.8; previous revision: 1.7
done
Comment 2 Quy Nguyen 2008-01-30 07:08:29 UTC 
The fix for this issue was reverted in Issue 125965.  Another solution is needed.
Comment 3 Winston Prakash 2008-02-04 15:18:30 UTC 
designer/jsf now calls UIComponent.rendersChildren() via InSyncServiceProvider ->
FacesContainer.isComponentRendersChildren(), which correctly sets the FacesContext first. 

Therefore, reverting the fix for the memory leak again.