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.
Thank you for your response.
Unfortunately, we do not have a Samsung Galaxy Tab device to test on, but I do have a device that runs Android 4.4.2. I have also tried on an emulator for the Galaxy Tab, but I have not been able to reproduce this issue. I will consult with our engineering staff to see if this may have been fixed internally. I will update you again shortly.
I have spoken with our engineering and development staff, and they believe that the issue you are seeing is fixed internally. The likely cause of this is specific to your data, since certain Android devices have higher resolutions that may cause a StackOverflow when loading specific 'shapes' of data.
Being that I am currently unable to reproduce this issue that you are seeing, would it be possible for you to please provide a sample data set or a sample project that reproduces this error on your device, so that I can test this issue more accurately?
Just checking in, did you have any other questions or concerns on this matter?
I'm still seeing the crash, but I haven't had time to preserve a sanitized dataset that replicates it for you. For now I'd like to keep this open until we either see an updated build that I can validate here or until I have time to get you a standalone reproduction.
Thanks.
I will keep this forum thread active until your next response. In the meantime though, it may be beneficial for us regarding this issue if you were to test the sample I created on your device which is receiving this exception. I have attached the sample project. Please test this on your machine and let me know what results you find. Or, if this sample application does not accurately demonstrate what you are trying to do, feel free to modify it and send it back.
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://es.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.
Hi Andrew, that's great news. Thank you.
We only use the Android components, no Xamarin Forms.
Ben
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?
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/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.