On 11 May 2015, at 11:05, Max Rydahl Andersen wrote:
Hey,
Just reading through some recently closed memory leak bugs in Eclipse
Platform and realising
how easy it is to forget to set references to null in ones dispose()
method sometimes ;)
The bug is at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436225
and gerrit is at
https://git.eclipse.org/r/#/c/36201/17
What is noticeable here its the fixes are mainly about ensuring not to
hold on to a selection forever
in a view. It will slowly but steadily leak over time.
Just a reminder to check ones dispose() and listener methods ;)
ha...a few seconds after I posted this it turns out the fix here
caused massive regressions since there code expect some of this state to
always
be there.
lesson of story - don't rely on state, always have a fallback plan ;)
/max
http://about.me/maxandersen