[Bug] FATAL EXCEPTION

[iplly]

Describe the error
The application crashed with an error

For playback
Steps to reproduce the behavior:

1. Scrolling through the application failed

** Relevant information:**

• Device: Oneplus 9r

• Android Version: 14

• ROM: crDroid 10.4

• Application version: 1.0.5

• Which installer did you choose? root

---

** Additional notes**
FATAL EXCEPTION: main Process: com.machiav3lli.fdroid, PID: 19143 java.lang.OutOfMemoryError: Failed to allocate a 72 byte allocation with 34424 free bytes and 33KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC. at android.database.CursorWindow.nativeGetString(Native Method) at android.database.CursorWindow.getString(CursorWindow.java:465) at android.database.AbstractWindowedCursor.getString(AbstractWindowedCursor.java:54) at com.machiav3lli.fdroid.database.dao.ProductDao_Impl$getFlow$1.call(SourceFile:91) at androidx.room.CoroutinesRoom$Companion$createFlow$1$1$1.invokeSuspend(SourceFile:81) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8) at kotlinx.coroutines.DispatchedTask.run(Unknown Source:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) at java.lang.Thread.run(Thread.java:1012) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.ui.platform.MotionDurationScaleImpl@e0376d7, androidx.compose.runtime.BroadcastFrameClock@6f94bc4, StandaloneCoroutine{Cancelling}@ad32aad, AndroidUiDispatcher@1b811e2]

• If you are using the latest test version (on the TG channel or in the Matrix Room), please report it directly there, not here.

• If you are using the latest version of github:

  • Please review the issues if they match yours, leave a comment if you can provide additional information.

• If you are not using the latest version of github (it takes several days to update the official F-Droid builds). Update, then make sure the error is still there. If so, keep reporting it.

Thanks for the message!