Hello everyone, I have a webgrid that sits in a warp to handle the postbacks generated by an ultraClacManager attached to the grid. This combination of controls causes a memory leak in IE, IE consumes about 1000 - 2000k per trapped postback and grows without limit. This has been identified originally as a bug by Infragistics as BR26172. My Question to anybody that has run into this problem is; have you found a work around short of removing the warp and asynchronous postbacks? I have tried wrapping the grid in an ASP.NET UpdatePanel however the Ajax extensions seem to be incompatible with the infragistics controls. This bug has delayed the move to production for 2 months now and we all know this is not good. Any help or incite would be greatly appreciated. Thanks in advance,Patrick
Nice, Thanks for the info.
I post updates on my blog whenever there is information about hot fixes to be published, including upcoming release dates. You can view the relevant blog posts here.
That's good news. Thanks for all your help on this issue. Any word on when the public release will happen?
Patrick
I just looked up the bug info and see that this is marked as fixed and for release in the next public hotfix.
Patrick, I'm not sure why you never received any updates on the status of the bug, though I fear it is my fault. Because I went around the standard channels to get you the private fix, your name was probably never associated with the bug. My appologies.
Here's the relevant info:
Fixed in Versions: 6.3.20063.1090 CLR 1.x, 6.3.20063.1090 CLR 2.0, 7.1.20071.1066 CLR 1.x, 7.1.20071.1066 CLR 2.0, 7.2.20072.1074 CLR 2.0, 7.3.20073.1048 CLR 2.0, 8.1.20081.1006 CLR 2.0, 8.1.20081.1006 CLR 3.5
To all: Be sure to contact out support team (www.infragistics.com/gethelp) to get "linked" to this and any other bug that you may encounter. That will get you on the autonotify list for all changes in bug status.
I'll see if I can find out what's going on here. It's possible that the private build had a regression issue that cropped up. Don't be fooled by memory drops when minimizing the browser - it's only reducing the workingset of memory used for the browser, it's not actually clearing up any objects.
-Tony