Every now and then and with no repeatable pattern, I get a red X in my application.
I develop an application with infragistic control .i build my application on 32 bit and my customer is upgraded to 64 bit operation system.
Is this the case i get out of memory exception and Red X occur.Please share view on this.
The big red X means that an exception was raised during the OnPaint of the grid. The most common cause of this kind of issue is that your application is using multiple threads incorrectly and so the grid ends up getting out of synch with it's own internal data or the data source it's bound to and this causes a crash. Is your application using a background thread?
Hello Mike,
Thanks for your reply .will you explain multiple threads in details.
Hello Tihomir ,
In my case most of the time Red X apprear ater giving message "index out of range" and "Out of memory Exception" .
An Index Out Of Range exception is consistent with a threading issue.
Out of Memory is not as consistent, but it still could be a threading issue.
Threading issues tend to present themselves arbitrarily at varying locations in the code, and then tend to cause Index Out Of Range exceptions because a collection is out of synch with it's own count when you access it on a separate thread.
Have you checked your code to see if you are using multiple threads?
On further dig into this we i found that the red x is occur only for specific window user ,when i log into window with different user and perform same activity than red x not occurred .please share your view on this.
Is Red X is releated with window user permission ?
Hello Deepak,
The red X is coming from an exception being thrown during the paint event of the control. Another user without the permissions may not be accessing the part of the code causing the problem, so taking a closer look at the exceptions you have mentioned in your previous post would be right approach.
Please let me know if you still have any questions.
I can't immediately think of any reason why a red X would be caused by running the application under a different user. At least nothing that is specific to the WinGrid. It might, of course, be some kind of permissions issue or something that isn't installed correctly.
It might help if you could post the call stack of the exception.