PDA

View Full Version : [OPEN] Large Memory Leak in Grid



cpswaim
25 Apr 2013, 7:06 AM
REQUIRED INFORMATION




Ext version tested:

Ext 4.2 rev 663


Browser versions tested against:

IE8
Chrome 25
Chromium 24


DOCTYPE tested against:

html


Description:
I have been working recently with large data sets (200-1000 rows), and have noticed that when I destroy or reconfigure a grid, there's always memory left over. I have tried every possible avenue (that I know of) to make sure that memory gets released. I have a sample of code here: http://jsfiddle.net/smQRL/

Why is the memory being held? I can refresh (reconfigure) the grid and watch the memory usage rise from the 80-100MB to as high as I want (300MB+) for a single grid.


Steps to reproduce the problem:

http://jsfiddle.net/smQRL/


The result that was expected:

Memory doesn't leak


The result that occurs instead:

Memory Leaks


Test Case:


http://jsfiddle.net/smQRL/






HELPFUL INFORMATION




Screenshot or Video:

attached


See this URL for live test case: http://




Debugging already done:

Tried to remove references from objects many different ways (for the objects I am visibly creating)
Tried different forms of Ext removal methods (remove, removeAll, destroy) on the grid, grid view, store, etc.


Possible fix:

not provided


Additional CSS used:

only default ext-all.css


Operating System:

Win7

slemmon
25 Apr 2013, 10:10 AM
Thanks for the report!
I've linked your report to an open ticket: EXTJSIV-8264

cpswaim
25 Apr 2013, 12:45 PM
Are there any suggestions on how to work around this for the time being? It seems the ticket number 8264 (if they increment) is about 1300 tickets behind the newest ones being given out (9500's for newer issues), so it may be a previously known issue?

This memory leak is a serious issue for my team's application (which makes heavy use of grids), and any mitigation techniques or advice would be greatly appreciated.

slemmon
26 Apr 2013, 11:49 AM
I'm afraid I don't have any advice for mitigation at this point. It is an open issue and being actively worked on, though, I can assure you.

Sorry for the pain it's causing you guys. We've confirmed the issue, but the issue itself is still being root-caused.

Thanks for your patience!

jchau
26 Nov 2013, 9:24 AM
any updates on this issue?