Bug 92561 - Leaked HistoryItems in DocumentManager?
Summary: Leaked HistoryItems in DocumentManager?
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 69338 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-25 06:06 EDT by Markus Keller CLA
Modified: 2005-05-06 06:01 EDT (History)
1 user (show)

See Also:

Attachments
references from DocumentManager (132.17 KB, image/png)
2005-04-25 06:07 EDT, Markus Keller CLA 		no flags Details
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 Markus Keller CLA 2005-04-25 06:06:34 EDT 
I20050420-1200

In a huge YourKit memory trace, I see that DocumentManager holds 303 Documents
in memory. I used local history before, but when I made the dump, no local
history dialog was up. 

YourKit says that the 'Retained size' of the array fgValues is 75,393,728 bytes.

[Snapshot on my machine: I20050420-1200_1.5.0_20050425_1004.memory]
Comment 1 Markus Keller CLA 2005-04-25 06:07:34 EDT 
Created attachment 20291 [details]
references from DocumentManager
Comment 2 Markus Keller CLA 2005-04-25 06:44:45 EDT 
I've used 'compare with local history' on a java method several times.

No compare editor was open, but the synchronize view had 2 synchronizations that
compared HEAD of a project with a previous tag.

Closing all editors and removing all synchronizations from the synchronize view
did not free the retained documents and did not remove the many HistoryItems.
Comment 3 Andre Weinand CLA 2005-04-25 11:19:24 EDT 
*** Bug 69338 has been marked as a duplicate of this bug. ***
Comment 4 Markus Keller CLA 2005-05-04 08:31:34 EDT 
FYI: I did not find any HistoryItems in snapshots of recent builds. The leak
could have been caused by differences in the sequence of part events sent out by
the workbench (which has caused problems in other areas, too). AFAIK, the
original behavior has been resored in the meantime.
Comment 5 Andre Weinand CLA 2005-05-06 06:01:31 EDT 
I've fixed a leak.