Community
Participate
Working Groups
JavaModelManager::discardWorkingPerCopyInfo seems to discard the cache-entries concerning the elements of the working copy immediately before building the delta of the working copy and the original. As building the delta involves inspecting elements of the working copy, this causes elements to be rebuilt, causing a performance hit. Is this the intended behaviour? (Have I missed some non-obvious constraints?)
The delta is being built in the case of a primary working copy only. In this case, the corresponding source on disk can be different than the source of the working copy. This is why we're re-reading the content of the source on disk. We could indeed optimize the case where the source is the same. In this case the delta will always be empty.
*** Bug 128430 has been marked as a duplicate of this bug. ***
Created attachment 34918 [details] Possible fix
Released patch to HEAD
Verified for 3.2M6 using build I20060327-0010.
*** Bug 91732 has been marked as a duplicate of this bug. ***