nihad640 / smartgwt

Automatically exported from code.google.com/p/smartgwt
0 stars 0 forks source link

TreeGrid Out of Memory Exception #638

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I believe I have found a memory bug with Internet Explorer using the Tree Grid. 
 When interacting with the Tree Grid I get an out of memory exception when 
clicking on the records in the Tree Grid.  I have posted my issue on the forums 
at:
http://forums.smartclient.com/showthread.php?p=75367#post75367
The bug seems to come from the shape of the tree.  In my test case I have a 
tree with 8000 nodes in the first row after the root and 2 leaves per node.  If 
I reverse this structure and have 2 nodes in the first row and 12000 leaves per 
node there is no issue.  I am using SmartGwt 2.5 and the issue only comes from 
Internet Explorer.  Attached are my test case and a copy of the exception. 

Original issue reported on code.google.com by nwgorets...@gtempaccount.com on 31 Oct 2011 at 3:00

Attachments:

GoogleCodeExporter commented 9 years ago
You've got autoFitData set to vertical auto-fit. This means the tree grid will 
render all 8000 rows into the DOM and auto-fit to them. If you turn that 
setting off, so the grid renders at the page height and renders incrementally, 
the problem goes away.
This seems to not be a realistic use case - can you clarify whether you're 
actually encountering this problem in a real use case, and if so what it is?

Original comment by smartgwt...@gmail.com on 1 Nov 2011 at 9:20

GoogleCodeExporter commented 9 years ago
I removed the autoFitData call but the behavior persists.  Also, leaving all 
the settings alone I can set the first level to 24,000 with no second level and 
the memory exception does not happen either.  This makes me believe it has 
something to do with the shape of the tree, not simply the number of nodes on 
the tree.  This is a simple example but it does represent a real-world use 
case.  In an asset management system I'm working on it is not uncommon to have 
large numbers of asset categories with only a few sub-categories under each 
category.

Original comment by nwgorets...@gtempaccount.com on 2 Nov 2011 at 1:09