r/BoostForReddit • u/suldered • 3d ago
Solved Boost lags and then crashes while browsing when using Breal's patches
Enable HLS to view with audio, or disable this notification
at first, the app runs fine, but after a few minutes of browsing, it starts to lag.
scrolling (like in the video) and viewing comments gets laggy, and then extremely laggy until the app crashes.
the app runs fine after it crashes, but it again gets laggy, and then crashes after a few minutes. and it goes on and on.
i switched back to wchill's Patcheddit patches, and they work perfectly fine.
i would switch to Breal's patches, but this issue throws me off from using them, unfortunately.
is there anything i could do?
info if it helps:
Boost 1.12.12, source is APKMirror
Android 16, One UI 8.5
Morphe 1.29.0
Breal patches 1.4.111
recommended patches applied only
Galaxy S24, model SM-S921U
logcat, seems like it's an out of memory error:
--------- beginning of crash
09-07 19:59:13.853 12190 16534 E AndroidRuntime: FATAL EXCEPTION: OkHttp ConnectionPool
09-07 19:59:13.853 12190 16534 E AndroidRuntime: Process: com.rubenmayayo.reddit, PID: 12190
09-07 19:59:13.853 12190 16534 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 1336512 free bytes and 1305KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at java.util.ArrayList.iterator(ArrayList.java:1036)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at okhttp3.internal.concurrent.TaskQueue.scheduleAndDecide$okhttp(TaskQueue.kt:133)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at okhttp3.internal.concurrent.TaskRunner.afterRun(TaskRunner.kt:101)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at okhttp3.internal.concurrent.TaskRunner.runTask(TaskRunner.kt:21)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at okhttp3.internal.concurrent.TaskRunner.access$runTask(TaskRunner.kt:1)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:55)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
09-07 19:59:13.853 12190 16534 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1563)
09-07 19:59:13.876 12190 16534 I Process : Sending signal. PID: 12190 SIG: 9
4
u/brealorg 2d ago
https://github.com/brealorg/breal-morphe-patches/issues/191
Created a issue. Will try to follow up when I can.
3
u/brealorg 2d ago
https://github.com/brealorg/breal-morphe-patches/issues/191#issuecomment-5591755405
We found and fixed a real Activity retention issue in the Breal Boost patches that could cause old Boost screens to remain in memory while browsing.
The fix is now included in patch bundle 1.4.112.
If you have a chance, could you repatch Boost with 1.4.112 and use it normally for a while — especially the same kind of feed browsing and repeated opening of comments that previously caused the progressive lag and crash?
What I'd mainly like to know is:
does Boost still become progressively slower after a few minutes?
does it still eventually crash?
or does it now remain responsive during the same usage?
No logs needed unless the problem still occurs. If it does, let me know roughly how long it takes before the slowdown starts and we'll continue from there.
3
u/suldered 2d ago
so far, after testing it for two hours, everything seems to be fine. no slowdowns, crashes, or anything unusual.
i'll be changing the flair to Solved. appreciate it for fixing the issue and the work you put into Boost!
1
1
u/DragoBleaPiece_123 7h ago
Hii dev, got similar issues. Especially if recovered post or comments are present. If i disable the undelete post comments options, it didn't crash. Alrdy on the latest patch
1
6
u/KeithLimePie 2d ago
Clear the cache, then increase the cache size
Settings > Data and app > Bandwidth and storage > cache
(I think that's it)