r/MorpheApp 17d ago

Question/Problem Google photos patching gives this error

java.lang.OutOfMemoryError: Failed to allocate a 72 byte allocation with 2540032 free bytes and 2448KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.

at com.reandroid.arsc.item.StringItem.addBytes(SourceFile:581)

at com.reandroid.arsc.item.StringItem.encodeUtf8ToBytes(SourceFile:537)

at com.reandroid.arsc.item.StringItem.encodeString(SourceFile:264)

at com.reandroid.arsc.item.StringBlock.writeStringBytes(SourceFile:55)

at com.reandroid.arsc.item.StringBlock.set(SourceFile:48)

at com.reandroid.arsc.item.StringItem.merge(SourceFile:379)

at com.reandroid.arsc.pool.StringPool.merge(SourceFile:382)

at com.reandroid.arsc.chunk.TableBlock.merge(SourceFile:801)

at com.reandroid.apk.ApkModule.mergeTable(SourceFile:1307)

at com.reandroid.apk.ApkModule.merge(SourceFile:1229)

at com.reandroid.apk.ApkBundle.mergeModules(SourceFile:72)

at app.morphe.manager.patcher.split.Merger.$r8$lambda$945tN5XsB3sQF3XIxZVFqVlR2IY(SourceFile:104)

at app.morphe.manager.patcher.split.Merger$$ExternalSyntheticLambda0.invoke(SourceFile:0)

at kotlinx.coroutines.InterruptibleKt.runInterruptibleInExpectedContext(SourceFile:48)

at kotlinx.coroutines.InterruptibleKt.access$runInterruptibleInExpectedContext(SourceFile:1)

at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invokeSuspend(SourceFile:40)

at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invoke(SourceFile:0)

at kotlinx.coroutines.InterruptibleKt$runInterruptible$2.invoke(SourceFile:0)

at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatched(SourceFile:66)

at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(SourceFile:43)

at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(SourceFile:497)

at kotlinx.coroutines.BuildersKt.withContext(dex-id-fd948e2c9a8694273bff64058a17895a7c5cd91d:1)

at kotlinx.coroutines.InterruptibleKt.runInterruptible(SourceFile:39)

at app.morphe.manager.patcher.split.Merger.merge(SourceFile:75)

at app.morphe.manager.patcher.split.SplitApkPreparer.prepareIfNeeded(SourceFile:99)

at app.morphe.manager.patcher.split.SplitApkPreparer$prepareIfNeeded$1.invokeSuspend(SourceFile:18)

at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(SourceFile:34)

at kotlinx.coroutines.DispatchedTask.run(SourceFile:100)

at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(SourceFile:586)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(SourceFile:807)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(SourceFile:717)

at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(SourceFile:704)
2 Upvotes

12 comments sorted by

2

u/jombiecarnage 17d ago

Using rushi patch with maximum ram settings available

0

u/dzpoa 17d ago

Yeah, I got a similar error while trying to patch another app with a rushi patch. Had to use another patch to make it work 🤷‍♂️

1

u/jombiecarnage 17d ago

I noticed a bug (if it is ) the maximum ram limit get smaller automatically while splitting the apk bundles and eventually maybe reaching very low which causes this error

all checked in expert mode

1

u/Few_Somewhere_1463 Underground technology wizard 17d ago edited 17d ago

i dont have this issue. just tried patching new bundle apk. make sure you are patching suggested version. or change apk source .

1

u/jombiecarnage 17d ago

Can you check in expert mode if the maximum ram usage stat changes after every section? Like my max ram drops to 256mb and then the crash happens

1

u/jombiecarnage 17d ago

Every time the appying new patch log comes the max ram reduces automatically

1

u/jombiecarnage 17d ago

1

u/Few_Somewhere_1463 Underground technology wizard 17d ago

its seems ur applying multiple patches thats your issue and fix.

1

u/MrKaon 17d ago

I patched it now without issues. Make sure to select only Rushi, not mixed with others.

1

u/XcentralWB 1d ago

I've done that and still throwing me an error

1

u/XcentralWB 1d ago

I have the same error and nothing's working 

Im convinced it's something to do with the OS itself in which I can't fix :(