[
https://issues.apache.org/jira/browse/NIFI-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911604#comment-17911604
]
Matt Gilman commented on NIFI-5548:
-----------------------------------
I think the issue may have misdiagnosed as a memory leak. There was an issue
where the browser tab would appear hung. I'm fairly confident that issue was
due to NiFi attempting to re-render the canvas while polling with the browser
tab in the background. With the tab in the background, those attempts to render
the SVG would be queued up. Once enough of these requests queued it would
prevent the tab from becoming active again.
This issue was addressed in a PR for this ticket [1]. I have not experienced
this behavior since landing this fix.
[1] https://issues.apache.org/jira/browse/NIFI-13534
> Memory leak in graph user interface
> -----------------------------------
>
> Key: NIFI-5548
> URL: https://issues.apache.org/jira/browse/NIFI-5548
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.6.0, 1.7.0
> Environment: Chrome, Firefox
> Reporter: Alex A.
> Priority: Minor
>
> When the graph interface is left up on a browser tab for an extended period
> of time (several hours) the client RAM usage continues to grow to the point
> where the page no longer responds. This behavior has been observed in both
> versions of Firefox and Chrome on Windows 7 clients and throws an
> unresponsive script error attributable to the d3.min.js library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
