Fixed Memory Leak that caused keeping EventsManagerImpl for the whole run #3703
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PhysSimEventWriter
which keeps a reference to the EventManager to the matsim controller listeners we add a small object that keeps a reference only to a terminated threadpool.PrallelEventManagerImpl
multiple times because it abandons blocked threads that are GC Roots. They keep their frames until the app exits.vmInformation.writeHeapDump
in order to write a heap dump at each iteration so that we could debug memory leaks easier.This change is