Community
Participate
Working Groups
AnnotationModel.fModificationStamp is assigned to the last AnnotationModelEvent instance and thus holds back references to annotations contained in the change (until the next event is created). This is bad if an annotation itself contains references to "expensive" resources which would otherwise be garbage collected. See also bug 331232 for such a case. The fix should be simple and safe: Just assign a new Object() instead of the model event.
Created attachment 195579 [details] Suggested fix
Looks good, but we're already in RC2. Do you need this for 3.7 or is 3.8 good enough?
I guess 3.8 is sufficient.
We could also put it in 3.7.1 if that helps.
(In reply to comment #4) > We could also put it in 3.7.1 if that helps. Yes, thanks, that would be even better.
Comment on attachment 195579 [details] Suggested fix Committed to HEAD with the following update to the copyright header: Anton Leherbauer <anton.leherbauer@windriver.com> - [implementation] AnnotationModel.fModificationStamp leaks annotations - http://bugs.eclipse.org/345715
Fixed in R3_7_maintenance.
Verified in M20110810-0800.