History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-25380
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Dmitry Shaporenkov
Reporter: Dmitry Shaporenkov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

Race condition in ChangeManagerImpl

Created: 06 Aug 06 17:37   Updated: 06 Aug 07 10:14
Component/s: None
Fix Version/s: 2.0.1
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
 
This issue is duplicated by:
RSRP-24070 Assertion in ChangeManagerImpl.OnProv... Blocker Closed

Build: 244
Fixed in build: 254
Old URL: http://www.intellij.net/tracker/resharper/viewSCR?publicId=25380


 Description  « Hide
There is a rarely occurring race condition - if an event is being dispatched in the main thread, providers and dependency registration is delayed, and upon completion of change, all delayed registration actions are executed. Because of lack of synchronization, it may happen that order of registration actions inside one thread of execution is broken and the dependency gets registered at a moment when one of the participating providers (normally a document) has not been registered yet.

See e.g. http://www.intellij.net/tracker/resharper/viewSCR?publicId=25251

How to fix: even if there no change currently being dispatched, always execute all pending actions before registering provider / dependency.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.