Hi there,
I've got a WHDG set up with 250 rows bound to it. When I group by a column, the memory usage of firefox goes up by 20mb. When I remove the group by filter, it goes up by another 20mb. I can continue this cycle until my computer runs out of available memory. Is there any way to avoid this?
The other browsers fair a little better. IE8 jumps up 8mb each group by / un-group by, and Chrome jumps ~10mb each time.
Thanks!
Hi kslone,
What version of Firefox are you using? What version and build number do you have for the WebHierarchicalDataGrid? Is it just a WHDG grid on the page or are there other objects? Is it Ajax or a full postback? Update Panel? Sorry for all the questions, just trying to get a better idea.
regards,David Young
AgentD5 said:What version of Firefox are you using? What version and build number do you have for the WebHierarchicalDataGrid? Is it just a WHDG grid on the page or are there other objects? Is it Ajax or a full postback? Update Panel?
Hello kslone,
Can you please provide the requested by "AgentD5" information in order to help us identify and investigate reported by you behavior?
Thank you.
My firefox version is 3.6.13, but the problem occurs across multiple browsers (although firefox is the worst offender). The dll version for the Infragsitics library is 10.1.20101.1011. There are other objects on the page. It's an asynchronous operation contained within an update panel.
I have made an example following your description and I was unable to reproduce the described by you behavior. I have tested the example with IE 7&8, Firefox 3.6 and Google Chrome and build 10.1.20101.1011.
Created by me example is with 500 rows and the maximal memory usage for Firefox did not exceed 90-100MB after non-stop grouping and ungrouping for two minutes.
You can download example from here - http://community.infragistics.com/members/AEftimov/files/Samples/WHDGridGroupTest-_2D00_-kslone.zip.aspx
Feel free to test and modify it in order to achieve described by you behavior.
Please let me know if you have any further questions.
Sounds like there's an incompatibility with one of the other controls on the page. I'll investigate further. Thanks!
Feel free to contact me again if you need any further assistance regarding your question or the example.