Open GoogleCodeExporter opened 8 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
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
Original issue reported on code.google.com by
nwgorets...@gtempaccount.com
on 31 Oct 2011 at 3:00Attachments: