[ https://issues.apache.org/jira/browse/BEAM-6440?focusedWorklogId=185826&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-185826 ]
ASF GitHub Bot logged work on BEAM-6440: ---------------------------------------- Author: ASF GitHub Bot Created on: 16/Jan/19 15:23 Start Date: 16/Jan/19 15:23 Worklog Time Spent: 10m Work Description: mxm commented on issue #7530: [BEAM-6440] Fix leakage of timer de-duplication map URL: https://github.com/apache/beam/pull/7530#issuecomment-454818263 FYI This is backported from https://github.com/apache/beam/pull/7517. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 185826) Time Spent: 1h 50m (was: 1h 40m) > FlinkTimerInternals memory leak > ------------------------------- > > Key: BEAM-6440 > URL: https://issues.apache.org/jira/browse/BEAM-6440 > Project: Beam > Issue Type: Bug > Components: runner-flink > Affects Versions: 2.9.0 > Reporter: Thomas Weise > Assignee: Maximilian Michels > Priority: Major > Fix For: 2.10.0 > > Attachments: image-2019-01-15-10-31-43-618.png, > image-2019-01-15-10-41-08-200.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > After running a portable streaming app for 2-3 days, we see heap space > exhausted. Memory analysis shows large number of TimerData objects referenced > by heap state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)