[Dashboard] memory leak, some jQuery Object, Promise objects cannot be GC after refresh

[susan51531]

Kibana version:kibana-5.0.0-alpha5-linux-x86_64

Elasticsearch version:elasticsearch-5.0.0-alpha5

Server OS version:Ubuntu 14.04.5 LTS

Browser version:Version 53.0.2785.116 (64-bit)

Browser OS version:Ubuntu 14.04.5 LTS

Original install method (e.g. download page, yum, from source, etc.):dowload tar files from https://www.elastic.co

Description of the problem including expected versus actual behavior:
Expect: Newly created Objects should be GC after the next refresh;
Actual: After each refresh, there are still some objects have not been GC. This lead to memory usage keep growing.Chrome Tab will crash when keeping dashboard auto refresh;
Steps to reproduce:
1.open chrome in incognito mode
2.create a new dashboard, add a visualization
3.open chrome devtools, goto devtools's profile panel, start Record Allocation Timeline
4.set auto refresh interval to 5s, enable autorefresh
5.observing Allocation Timeline

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):
Recorded Profile:Heap-20160923T155153.heaptimeline

Constructor list:

A Object:
A Deferred Object:

I also tested the following kibana versions, this issue still exists.
Tested kibana versions:
kibana_4.1.11
kibana_4.2.2
kibana_4.5.4
kibana_4.6.1

[tangyong]

+1, the same issue regardless of auto-refresh.

[doudou0601]

The same version of the problem

[tangyong]

@spalger the issue should be same with the #3188 , and we found that in the latest version of Kibana, client-side memory leaks still happened. So, please seeing it again. Thanks!

[erikanderson]

+1 Any progress on this?

[rspython-zz]

+1 this is still happening on 5.2

[ameiji]

I can confirm the memory leakage problem in chrome with Kibana 5.4.1

[metametaclass]

It`s the same issue: #7427

[stacey-gammon]

Closing as a duplicate of #7427. I know this issue was created earlier but that one has more comments in it.