Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 464848 - Editors are not closed when project is closed after workbench restart
Summary: Editors are not closed when project is closed after workbench restart
Status: CLOSED DUPLICATE of bug 41431
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 4.5 M7   Edit
Assignee: Andrey Loskutov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-17 03:31 EDT by Karsten Thoms CLA
Modified: 2015-04-22 15:12 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Thoms CLA 2015-04-17 03:31:04 EDT
Steps to reproduce:
1) Start a runtime Eclipse instance
2) Create a simple project
3) Create two files in this project (e.g. test1.txt, test2.txt)
=> The editors for these files should now be opened
4) Restart Eclipse
=> The editors should now be still open
5) Close the project

The effect is that only the editor that has the focus is closed. The second editor will stay open and shows "Resource '/Test/test1.txt' does not exist."

It is expected that all editors are closed for resources of the closed project.


What I did observe is that FileDocumentProvider#createElementInfo is only called for the editor that has the focus on workbench restart. Thus, the second editor does not get a resource change event to close itself.
Comment 1 Lars Vogel CLA 2015-04-17 03:32:53 EDT
Karsten, thanks for the report. Can you post your Eclipse build ID?

Andrey, can you have a look?
Comment 2 Andrey Loskutov CLA 2015-04-17 03:56:08 EDT
Cannot reproduce with Build id: N20150413-2000.
@Karsten: which build do you use?
Comment 3 Andrey Loskutov CLA 2015-04-22 15:12:41 EDT
@Karsten: feel free to reopen if this does not work in the recent nightly builds, but otherwise it just looks like a dup of bug 41431.

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