Telegram's latest 10.10.1 image crashes when using graffiti. Grasping crash log shows an error in java. lang. OutOfMemoryError

[wfjun]

Select Topic Area

Bug

Body

FATAL EXCEPTION: main
Process: org.telegram.messengeres, PID: 20832
java.lang.OutOfMemoryError: Failed to allocate a 26542099 byte allocation with 25384672 free bytes and 24MB until OOM, target footprint 536870912, growth limit 536870912
at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
at java.nio.DirectByteBuffer$MemoryRef.(DirectByteBuffer.java:70)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:260)
at org.telegram.ui.Components.Paint.Painting.(Unknown Source:40)
at org.telegram.ui.Components.Paint.Views.LPhotoPaintView.(Unknown Source:187)
at org.telegram.ui.PhotoViewer$60.(Unknown Source:23)
at org.telegram.ui.PhotoViewer.createPaintView(Unknown Source:152)
at org.telegram.ui.PhotoViewer.switchToEditMode(Unknown Source:2064)
at org.telegram.ui.PhotoViewer.lambda$setParentActivity$29(Unknown Source:41)
at org.telegram.ui.PhotoViewer.$r8$lambda$Qnm8PB2dHFpuxX1Uimt0qGfk3z0(SourceFile:0)
at org.telegram.ui.PhotoViewer$$ExternalSyntheticLambda26.onClick(SourceFile:0)
at android.view.View.performClick(View.java:7528)
at android.view.View.performClickInternal(View.java:7505)
at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0)
at android.view.View$PerformClick.run(View.java:29525)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:242)
at android.os.Looper.loop(Looper.java:374)
at android.app.ActivityThread.main(ActivityThread.java:8907)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:671)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:951)

[Akash1134]

Hi @wfjun ,

Thanks for being a part of the GitHub Community, we're glad you're here!

If you're looking for help for this specific topic, you might want to try asking for help somewhere that focuses on this project, such as this one. It's possible that another GitHub user might have run into this same issue and can help, but the GitHub Community Discussions focuses primarily on topics related to GitHub itself or collaboration on project development and ideas. We want to make sure you’re getting the best support you can, but this space may not be the right place for this particular topic.

Best of luck!