Hi all,
I've witnessed this big red cross appearing in place of an UltraGrid when calls wern't marshalled correctly to the main/UI thread when making use of the control.
I have an application that I've ensured only accesses controls from the main/UI thread.
Recently, we've been stress-testing our application and have witnessed this red cross again. This time it appears in place of a ribbon/toolbar control. It's only ever appeared when we're using excessive amounts of memory - causing some components of the application to become sluggish. One example is when the user creates a scatter UltraChart component that has about 40,000 points of data.
So I have a couple of questions concerning this issue:
I'd appreciate any more information regarding this red cross. From what I've read so far:
Any information what so ever (even simply to clarify my current understanding is correct) would be greatly appreciated.
Cheers,
Richard
Hello Johnie,
I'm attempting to reproduce the issue you described, but I'm not able to. Which version of Windows are you using?
Mike,
My colleague has done some research on this and found that the problem is likely related to a GDI Memory Leak (http://megakemp.com/2009/02/25/gdi-memory-leak-in-windows-forms/).
Infragistics.Win.FormattedLinkLabel.PositionElementsCache contains a function with this signature:
private SizeF MeasureTextGDIOrThemed(string text, Font font, TextFormatFlags textFormatFlags), which does exactly what the link I provided says.
If I understand the article correctly, this signature is not disposing of 1 and possible 2 pointers:
IntPtr hObject2 = NativeWindowMethods.SelectObject(hdc, hObject);and if this needs cleaned up, then I would assume the following line would need to be cleaned up as well:NativeWindow.Methods.SelectObject(hdc, hObject2);
Mike: Please pass this onto your developers, as this signature appears to be the same in Infragistics4.Win.v13.2.dll
Thanks,Johnie Karr
As far as I know, we never got a sample, so we were never able to duplicate the issue in response to this forum post. But I wouldn't be surprised if the same issue came up from another customer and the issue was fixed a long time ago. I haven't heard any recent reports of a big red X in this control. The only way to know for sure is to try it with the latest version. You could download a trial version and try it out.
I have the same issue with 2010 Volume 2 version the same call stack. Was it identified and rectified in the other release?
Thanks Mike, I'll keep an eye out for it and when I get a chance I'll post a sample. Thanks for your help.