Bug 266 - Sync view memory leak (1GKKUIK)
Summary: Sync view memory leak (1GKKUIK)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: James Moody CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 2907
Blocks:
  Show dependency tree
 
Reported: 2001-10-10 21:39 EDT by John Arthorne CLA
Modified: 2017-08-29 15:33 EDT (History)
0 users

See Also:

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 John Arthorne CLA 2001-10-10 21:39:11 EDT 
It looks like the sync view has a memory leak. When the sync view is closed, all the model
objects stick around even after a full garbage collection (use OptimizeIt).  This is a lot of 
objects, and can represent a substantial leak for users that frequently open and close the
sync view.  With some poking around, I think I've found the source of the bug in the compare
framework.  However VCM team should track it to make sure it is indeed a compare FW bug, and that
it gets fixed.  Here is the PR I logged against compare:

	1GKKUA5: ITPUI:WINNT - Severe: memory leak in sync view



NOTES:
Comment 1 DJ Houghton CLA 2001-10-23 23:49:43 EDT 
PRODUCT VERSION:

Build 0.131
Comment 2 James Moody CLA 2001-11-14 11:16:55 EST 
The compare bug has been fixed. With some simple println debugging 
before/after, it appears that the object models are being properly garbage 
collected.
Comment 3 Eclipse Genie CLA 2017-08-29 15:33:57 EDT 
GitHub Pull Request 267 created by [cxbrooks]
https://github.com/eclipse/triquetrum/pull/267