Community
Participate
Working Groups
As discussed, this could be solved by: 1. extending IQuickDiffReferenceProvider with something like: canHaveChanges(), where initialization could be skipped if this returns false - this would also avoid the document copies for the background job 2. returning a proxy to the input document on getReference() and redirect the proxy on the first document change - this would avoid the additional memory consumption of the reference document while code browsing, could add costs to the first document change
Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug.
Is this going to be implemented for R3.1? Note that, if new API is required, you need to get the approval of at least one PMC member, at this point.
We should try to find improvements that work for all quick diff reference providers since most people probably use a team quick diff reference provider. Adding API that only improves the LastSaveReferenceProvider isnt' desirable.
*** Bug 133478 has been marked as a duplicate of this bug. ***
We could defer the read but we cannot get rid of it i.e. we can't use the yet unchaged document because this would result a blocked UI.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
