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.
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.
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."