[jira] [Commented] (NIFI-5548) Memory leak in graph user interface

["Matt Gilman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590328#comment-16590328 ] 

Matt Gilman commented on NIFI-5548:
-----------------------------------

[~aaversa] Thanks for reporting this! I was hoping you might be able to offer some more details regarding the behavior your seeing. Unfortunately, I don't have access to a Windows 7 machine and I'm not sure what versions of Firefox and Chrome you're using so I'm not sure I can reproduce exactly what you're seeing. I'm hoping you might be able to help with the debugging process to isolate where the underlying issue may be. I have been using the memory profiler in Chrome's Dev Tools to try to locate the problem but haven't observed it yet. I am running Chrome 68.0.3440.106 on OSX 10.13.6.

Was the canvas not being interacted with at all? The page was simply left open and the canvas continually polling for updated stats?
What is your flow like? 
Which components are used?
Was the canvas zoomed in close enough to render the component details?
How many components were on screen (and one screen in every direction)?
Did the number of components on screen make a difference for the behavior you saw?
How were you measuring client RAM usage?

When your browser is experiencing this, would you be able to investigate further using the Memory features of your browsers Dev Tools? This may be helpful [1].

[1] https://developers.google.com/web/tools/chrome-devtools/memory-problems/

> 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 Aversa
>            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
(v7.6.3#76005)