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.
Just found another clue. The exception only occurs when you have any type of row active (be it data or group). if there are no active row the expand seems to work fine.
Hi,
To my understanding, you are encountering an exception when you call the ExpandAll method while the ActiveRow property is set to anyone of the UltraGridRow objects on your grid. We will be happy to assist you further with this issue; however, we will require additional information that can be used to isolate the cause of this issue. As mentioned by Mike Saltzman, please attach a stack trace or sample that reproduces this issue. This will allow us to have the information needed to assist you further.
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.
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.
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?
Hey Mike, thanks for keeping me up on this. Yeah i was being dumb about the call stack, i was hitting "Continue" instead of "OK", which was causing the app to shut down and the stack to disappear. I attached the entire stack (at least what VS could hold). I am currently working on trimming down a sample project also. Oh, and i am definitely not doing anything with threading, i have seen your numerous warnings against such things as it pertains to grids :)
Are you sure you have the latest SR? This looks just like an issue that was fixed.
If you have the latest, then my guess is that there is something going on here between filtering, grouping, and formula calculations. The interactions between those three can get extremely complex, because formulas (which are normally calculated asynchronously) have to be synchronously calculated before any filtering or grouping can be performed. I can see from the call stack that you are using formulas and GroupBy. Is there also filtering applied to your grid?
I'm pretty sure we are going to need a sample in order to look into this, because it's probably an incredibly complicated issue. :)
yeah it seems to work with the very latest service release. Dang, unfortunately that means quite a bit of work to get those deployed. Thanks Mike!
well look at that. we have 2038, and it looks like there is 2054 now. i checked the release notes and i dont see anything in there about the issue but i will try to upgrade and try it out. I guess you all stealth fixed it :)
Also... I just took another quick look at the code, and the call stack you have here doesn't match up to the current source code. Like I mentioned above, there was an issue like this which was fixed and I can tell from the call stack you have here that it's following a code path that no longer exists in the latest source, so I'm pretty sure you don't have the latest service release for 12.1.