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 86249 - Memory Leak caused by BPEL validator
Summary: Memory Leak caused by BPEL validator
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Alexey Yarmolenko
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 86250
  Show dependency tree
 
Reported: 2006-09-30 15:52 UTC by Chris Webster
Modified: 2007-08-15 20:02 UTC (History)
0 users

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 Chris Webster 2006-09-30 15:52:18 UTC
org.netbeans.modules.bpel.model.validation.imports.BPELImportsValidator has an
instance variable which refers to the last validation. This causes all the
referenced models to be strongly referenced until the next validation is
performed. This variable needs to either be removed or set to null following
validation to avoid a memory leak.
Comment 1 Alexey Yarmolenko 2006-10-02 10:34:46 UTC
Fix is quiet simple. .validation field is exposed thru .getValidation() method 
to all BPELImportsVisitors, which are calling this method during validation 
procedure. Cleaninig .validation field in the end of .validate method is 
sufficient fix for this bug.
Comment 2 Alexey Yarmolenko 2006-10-03 09:47:54 UTC
diff -r1.1.2.5.2.2 -r1.1.2.5
55c55
<
---
>         this.validation = validation;
70,71d69
<         this.validation = validation;
<
97,100d94
<
<         //Fix for IZ86249
<         //Release reference to last vallidation, causing memory leaks
<         this.validation = null;
Comment 3 Michael Frisino 2006-10-03 10:21:07 UTC
Reviewed fix. Looks trivial. Should commit to release55 and close.
Comment 4 Alexey Yarmolenko 2006-10-03 13:51:04 UTC
fix merged into release55 branch
Comment 5 _ hong_lin 2007-08-15 20:02:36 UTC
Close "FIXED" issue against previous releases