Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367467 - Generate Getters and Setters leaks memory
Summary: Generate Getters and Setters leaks memory
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-refactoring (show other bugs)
Version: 8.0.1   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 8.0.2   Edit
Assignee: Marc-André Laperle CLA
QA Contact: Sergey Prigogin CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-22 22:54 EST by Marc-André Laperle CLA
Modified: 2011-12-23 00:38 EST (History)
1 user (show)

See Also:

Attachments
Generate-Getters-and-Setters memory leak patch (1.04 KB, patch)
2011-12-23 00:08 EST, Marc-André Laperle CLA 		malaperle: iplog-
Details | Diff
View All 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 Marc-André Laperle CLA 2011-12-22 22:54:06 EST 
Tested with 8.0.1 and master as of 2012-12-21.

1. Open the Generate Getters and Setters dialog in multiple, different files
2. Run garbage collection
3. Run Eclipse Memory Analyser, look at the Dominator Tree

There's a few instances of org.eclipse.cdt.internal.core.parser.scanner.LocationMap (among other objects) that are not being GC'd because GenerateGettersAndSettersInputPage is still in the preferenceChange listeners.
Comment 1 Marc-André Laperle CLA 2011-12-23 00:08:58 EST 
Created attachment 208761 [details]
Generate-Getters-and-Setters memory leak patch
Comment 2 Marc-André Laperle CLA 2011-12-23 00:38:27 EST 
Fixed in 8.0.2 and master > 2012-12-22.