Hi there, I'm using the Infragistics Android trial release on a few devices (we have a license for iOS and Android too I think).
This crash in particular is on a Samsung Galaxy Tab 8.0 (GT-5110) running Android 4.4.2. I'm getting this crash when adding some amount (300-400 entries) of data to a DataChartView. The DataChartView has a RangeAreaSeries and an overlapping LineSeries.
As would typically happen with a stack overflow, we lose the actual root of the stack, unfortunately.
E/AndroidRuntime( 3327): java.lang.StackOverflowErrorE/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:487)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)E/AndroidRuntime( 3327): at com.infragistics.controls.Flattener.fastFlattenRecursive(Flattener.java:485)
Hello Ben,
Thank you for your post.
I am investigating into this issue to see if I can reproduce the StackOverflowError that you are seeing. It is also possible that this may have been fixed internally as well. I will update this thread again as soon as I have more information for you on this matter.
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support
Thanks. FWIW, I've only seen this on this specific device. I don't see the same crash ever running a Genymotion emulator (5.x and 4.x) or on my Nexus 5 running Android 5.1.
Caylan,
Looking at your stack trace it seems like you are running the safer code, but we may need to increase the protection against runaway stack depth due to lower stack limits on Android. If you could get that sample data to Andrew, if you haven't done that already, it should hasten our diagnosis.
-Graham
BTW, the largeheap recommendation I made in the other thread my apply here, since requesting a larger heap allocation may also result in a larger stack size limit. Since you can't reproduce the issue on every device, it likely means that this relates to total heap space and free heap space, since those can vary per device.
Here is a standalone repro for the fastFlatten stack overflow, at least for my Samsung Galaxy Tab 8. You might find the need to adjust the multiplier on the data in the MainActivity load method to get it to crash, depending on your device. I set it to 10, so 10 copies of the csv data in the app appended to each other. One copy wasn't enough for this device in this setup. Highly variable stuff.
https://dl.dropboxusercontent.com/u/56947838/FastFlatten.zip
Any update on this?
Hello Caylan/Ben,
I have been testing the standalone application that was provided, and I have reproduced this issue. I also noticed that after lowering the multiplier on the data in the MainActivity load and getting the application to startup, if you zoom in on the chart, the same exception is thrown. I am currently collaborating with Graham to see what can be done about this. I will update you again soon.
Great. Thanks for all your hard work! Our only concern is to have this fixed as soon as possible. This issue is a showstopper for our app release and we are a few days behind schedule because of it.
Hello Caylan,
We have internally created a parameter that can be set to solve this current issue you are having, and I just need to test it a little bit more before sending it, just to be sure. I will likely be creating a case tomorrow that will be viewable to Ben through which I will send a new private build. One thing though, are you using the Android components exclusively, or are you using Xamarin Forms?
Hi Andrew, that's great news. Thank you.
We only use the Android components, no Xamarin Forms.
Ben
Thank you for your response.
I have been testing out the private build, and it appears to solve the issues that you were having with the Flattener exception as well as the orientation flip OutOfMemory exception. I have created a case for you so that I can send you this private build. It has a case ID of CAS-152678-X1X7T7 and you can access it here: https://www.infragistics.com/my-account/support-activity. I will be sending an update to that case shortly with more information on the build changes, along with the private build attached to it.