Bug 233265 - Editor leaked after opening from Synchronize view and replacing with HEAD
Summary: Editor leaked after opening from Synchronize view and replacing with HEAD
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-21 12:01 EDT by Markus Keller CLA
Modified: 2019-09-06 16:15 EDT (History)
1 user (show)

See Also:

Attachments
Paths from GC roots to CompilationUnitEditor (84.49 KB, text/html)
2008-05-21 12:01 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 2008-05-21 12:01:03 EDT 
Created attachment 101303 [details]
Paths from GC roots to CompilationUnitEditor

I20080520-2000

- new workspace
- import org.eclipse.core.expressions from CVS
- set quick diff reference provider to CVS
- open type ElementHandler
- add a space somewhere and save
- close the editor
=> no editors leaked

- open Synchronize view
- create new Synchronization for workspace (all defaults, don't switch perspective)
- in Synchronize view, doubleclick ElementHandler.java
- from Synchronize view, drag ElementHandler.java to editor area
- when the quick diff is updated, choose context menu > Replace With > Latest from HEAD
- close editor (compare editor has been closed automatically)

=> Editor is leaked. Suspects:
  - RemoteRevisionQuickDiffProvider still registered as CVSWorkspaceSubscriber
  - site of TeamOperation$TeamOperationJobContext not null after job done
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:15:21 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.