Community
Participate
Working Groups
Build Identifier: ProgressViewUpdater keeps (by a few layers of indirection) references to all Jobs (or at least the ones we care about) so if a Job is an anonymous class or a non static member class then its reference to the parent class will keep that instance around forever as well. If a Job as in this case is only intended to be used once for a fairly brief period of time this results in a problem. I have a patch which fixes this up and stops GC errors when analyzing multiple exes in a row (such as during some testing) results in a GC error as all data is accumulated. Additionally DwarfDebugInfoProvider's dispose() method which would have mitigated this problem does not clear() all the things it should allowing references to everything to persist. I have a patch which fixes this. Reproducible: Always
Created attachment 202793 [details] Patch creating a static ParseJob class to do the anonymous inner class Job's work and fix dispose method
i've nominally tested this using our JUnit suite (including the edc JUnit suite), and have committed it to our local repository, pending final review and eclipse edc git merge by committer ken ryall.
(this is part of a batch change) The Eclipse CDT EDC (https://wiki.eclipse.org/CDT/cdt-debug-edc) is now obsolete and has not had any active development since 2011. Therefore the still open bugs are being marked as wontfix. The git repo for the project still exists for posterity at https://git.eclipse.org/c/cdt/org.eclipse.cdt.edc.git/
