Checklist
Affected version
0.28.0 i think? Maybe reproducible with newer version as well??
Steps to reproduce the bug
- open history
- open video there
- lock device
- unlock device
- open close history
- rinse-repeat...
Expected behavior
At some point video playback starts to stutter, then later it should crash
Actual behavior
As expected
Screenshots/Screen recordings
No response
Logs
OutOfMemoryError: Failed to allocate a 24 byte allocation with 595744 free bytes and 581KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
at j$.time.Instant.Z:413
at j$.time.Instant.ofEpochMilli:346
at org.schabi.newpipe.database.Converters.offsetDateTimeFromTimestamp:19
at org.schabi.newpipe.database.history.dao.StreamHistoryDAO_Impl$9.call:727
at org.schabi.newpipe.database.history.dao.StreamHistoryDAO_Impl$9.call:624
at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromCallable.subscribeActual:47
at io.reactivex.rxjava3.core.Maybe.subscribe:5377
at io.reactivex.rxjava3.internal.operators.flowable.FlowableFlatMapMaybe$FlatMapMaybeSubscriber.onNext:131
at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$ObserveOnSubscriber.runAsync:403
at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run:178
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run:324
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.runEager:289
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.run:250
at ThreadPoolExecutor.runWorker:1145
at ThreadPoolExecutor$Worker.run:644
at Thread.run:1117
Affected Android/Custom ROM version
Android 10 (OneUi 2)
Affected device model
SM-G570Y
Additional information
I forgot when did it happen, it was quite a while ago, i found it in my note (and i dumped it here rn bcz i wanna do some big maintenance stuff around my devices), i didnt write the app version, i cant reproduce it for now, if anyone else can reproduce do tell me :D
But i noticed the crash logs mention date time, and alsocrecent updates have date time related commits, in case its actually fixed or unreproducible, feel free to close this issue tho :/
Checklist
Affected version
0.28.0 i think? Maybe reproducible with newer version as well??
Steps to reproduce the bug
Expected behavior
At some point video playback starts to stutter, then later it should crash
Actual behavior
As expected
Screenshots/Screen recordings
No response
Logs
OutOfMemoryError: Failed to allocate a 24 byte allocation with 595744 free bytes and 581KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
at j$.time.Instant.Z:413
at j$.time.Instant.ofEpochMilli:346
at org.schabi.newpipe.database.Converters.offsetDateTimeFromTimestamp:19
at org.schabi.newpipe.database.history.dao.StreamHistoryDAO_Impl$9.call:727
at org.schabi.newpipe.database.history.dao.StreamHistoryDAO_Impl$9.call:624
at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromCallable.subscribeActual:47
at io.reactivex.rxjava3.core.Maybe.subscribe:5377
at io.reactivex.rxjava3.internal.operators.flowable.FlowableFlatMapMaybe$FlatMapMaybeSubscriber.onNext:131
at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$ObserveOnSubscriber.runAsync:403
at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run:178
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run:324
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.runEager:289
at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.run:250
at ThreadPoolExecutor.runWorker:1145
at ThreadPoolExecutor$Worker.run:644
at Thread.run:1117
Affected Android/Custom ROM version
Android 10 (OneUi 2)
Affected device model
SM-G570Y
Additional information
I forgot when did it happen, it was quite a while ago, i found it in my note (and i dumped it here rn bcz i wanna do some big maintenance stuff around my devices), i didnt write the app version, i cant reproduce it for now, if anyone else can reproduce do tell me :D
But i noticed the crash logs mention date time, and alsocrecent updates have date time related commits, in case its actually fixed or unreproducible, feel free to close this issue tho :/