Bug 54594 - Leaking CompilationUnitEditors
Summary: Leaking CompilationUnitEditors
Status: RESOLVED DUPLICATE of bug 53473
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-12 05:32 EST by Dirk Baeumer CLA
Modified: 2004-03-15 09:52 EST (History)
1 user (show)

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 Dirk Baeumer CLA 2004-03-12 05:32:10 EST 
I20040310

After a day of working I was leaking 64 compilation unit editors. I looked at 
the memory dump and strange things are happen. For example even the 
refactoring undo action is hanging onto an editor since its dispose method 
didn't get called when the editor closed.

So there might be a deeper problem in the workspace. I copied the memory dump 
to t\jabiru\memory-dumps\2004-03-12--10-47-56.ymp-snapshot
Comment 1 Thomas M??der CLA 2004-03-12 06:07:16 EST 
Just to make this explicit: Dirk say he closed all editors before taking the
snapshot.
Comment 2 Thomas M??der CLA 2004-03-12 06:22:00 EST 
There is a case where one reference to an editor might be retained by the new
search support after the editor is closed. It is never more than one reference
total, though, so there are still 63 to account for.
Comment 3 Dani Megert CLA 2004-03-15 09:52:00 EST 

*** This bug has been marked as a duplicate of 53473 ***