Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340561 - Dirty state manager does not release lock
Summary: Dirty state manager does not release lock
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: SR1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-21 08:34 EDT by Johan Wannheden CLA
Modified: 2017-09-19 17:20 EDT (History)
1 user (show)

See Also:
sebastian.zarnekow: indigo+

Attachments
Screenshot (52.13 KB, image/png)
2011-03-21 08:35 EDT, Johan Wannheden 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 Johan Wannheden CLA 2011-03-21 08:34:55 EDT 
Build Identifier: M20110210-1200

Opening a source in two editors and invoking content assist on one of them seems to aquire a lock on the source. Aborting content assist invocation (nothing modified), switching to the other editor and invoking content assist in a context causes the following pop-up message to appear (even though no editor is dirty!): "the resource is currently being edited in another editor".

Reproducible: Always
Comment 1 Johan Wannheden CLA 2011-03-21 08:35:20 EDT 
Created attachment 191611 [details]
Screenshot
Comment 2 Sebastian Zarnekow CLA 2011-07-29 17:23:52 EDT 
Pushed to master.
Comment 3 Karsten Thoms CLA 2017-09-19 17:08:37 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 17:20:11 EDT 
Closing all bugs that were set to RESOLVED before Neon.0