|144630||May 15,2019 11:04 AM UTC||Jul 6,2019 12:09 PM UTC||Xamarin.Forms||17|
Java.Lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available
at Java.Interop.JniEnvironment+StaticMethods.CallStaticObjectMethod (Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00069] in <09821b4f44794452b7d6c054ac9447f5>:0
at Java.Interop.JniPeerMembers+JniStaticMethods.InvokeObjectMethod (System.String encodedMember, Java.Interop.JniArgumentValue* parameters) [0x00018] in <09821b4f44794452b7d6c054ac9447f5>:0
at Android.Graphics.Bitmap.CreateBitmap (System.Int32 width, System.Int32 height, Android.Graphics.Bitmap+Config config) [0x0005a] in <788a34f7a7b84486905dfde786529d42>:0
at Xamarin.Forms.Platform.Android.BorderDrawable.CreateBitmap (System.Boolean pressed, System.Int32 width, System.Int32 height) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\BorderDrawable.cs:174
at Xamarin.Forms.Platform.Android.BorderDrawable.Draw (Android.Graphics.Canvas canvas) [0x000c9] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\BorderDrawable.cs:90
at Android.Graphics.Drawables.Drawable.n_Draw_Landroid_graphics_Canvas_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_canvas) [0x00011] in <788a34f7a7b84486905dfde786529d42>:0
at at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.61(intptr,intptr,intptr)
at java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available
Hi Andy,Thank you for contacting Syncfusion support.We have analyzed the reported issue "Memory leak in schedule Android and iOS" and it works fine from our end. We need ensure memory leak by navigate to any other page from schedule, and on this scenario there is no memory leak on schedule. We have tested the shared sample and it doesn't have any navigation to schedule on this scenario new view created for first three views then we have reused the already available view hence the memory will increase for first three swipes and it becomes stable.We have attached the sample with navigation page and the screenshot of tested results.Sample link: http://www.syncfusion.com/downloads/support/directtrac/general/ze/MONTHC~3-1144936942.zipPlease check the sample and revert us if you have any concern.Regards,
Subburaj Pandian V
We need ensure memory leak by navigate to any other page from schedule, and on this scenario there is no memory leak on schedule
I don't understand what you mean by needing navigation.
The sample I provided demonstrates the leak just by swiping through the months. There's no page navigation required.
As I have already commented, I also replicated the leak with your sample. I am concerned you are evaluating this as something to do with navigation.
One of the main features of the rewrite I'm doing with Syncfusion is to allow users to swipe from one month to the next - it is the main reason why many people stopped using the previous app.
Just to be clear, you have to swipe through many months to get a crash, at least 18. That seems consistent using your sample with the Button and my SkiaSharp views.
Note the amount of drawing inside SkiaSharp has no effect - I run out of memory at about the same time with an empty SKCanvasView or with a mix of shapes and text drawn in the cells. It is just a leak of the view.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"android:versionCode="1" android:versionName="1.0"package="com.companyname.monthcellcustmodern">
<uses-sdk android:minSdkVersion="21"android:targetSdkVersion="27" />
This post will be permanently deleted. Are you sure you want to continue?
Sorry, An error occured while processing your request. Please try again later.
This page will automatically be redirected to the sign-in page in 10 seconds.