Hello, i was just curious if anyone has seen this. we recently upgraded to version 12.1 and it seems that sometimes when using grid.Rows.ExpandAll(True), it will sometimes cause a stack overflow exception. It has been verified that this doesnt happen with the previous version we were using (10.3) on the same screen with the same data loaded. I have attached an image. the top part is showing the expand all working with the previous version, the second part is showing how it now throws an exception. We are just calling "clickedGrid.Rows.ExpandAll(true)" via a right click menu. This could make or break the next release of software for us as we have already implemented several new features requiring 12.1.
Hi,
If you have the latest service release, then I doubt upgrading to 12.2 will make any difference. This must be some new issue.
If you are certain that you have the latest SR, then the only other suggestion I can think of is that you post a small small sample project which duplicates the exception so we can check it out.
It might help if you were able to post the whole call stack, too. I'm not sure why you are unable to do that. If you can get to the call stack window, you can select everything and then copy and paste from it. If the window is closing automatically or something, then that could be an indication that this is a threading issue. Is your application using multiple threads?
Well i thought we were all up to date, but i notice that 2012 vol 2 is out now. We just upgraded from 10.3 to 12.1 (latest service release within that release). Since it was working in 10.3, does this mean it was something broken in between then fixed in 12.2? I can code a workaround to clear row selection prior to expand all and it seems to work, so i might have to do that since our upgrade to 12.1 hasnt even made it to production (and wont until december). And since we are in code freeze i wont be able to take us up to 12.2.
This looks like an issue that may already be fixed. Do you have the latest service release?
How to get the latest service release - Infragistics Community
If that doesn't help, perhaps you could post a small sample project here demonstrating the exception. It's probably related to some specific set of property settings in your grid.
i was able to undock my call stack window and maximize it in another window to get as much as i could when the error happens. As soon as i hit continue on the exception the app shuts down so i had to screenshot it. i wasnt able to scroll the call stack window with the error was up as it took focus.
Disassembly is a completely different thing. You are seeing the disassembly code because you don't have the source code, but that doesn't matter. There is still a stack trace. In fact, I could be wrong, but I'm pretty sure it's visible in the background of the screen shot you posted here on the lower-left hand side behind the View Detail Window.