Closed tSquaredd closed 2 years ago
@tSquaredd Thanks for reporting this and sorry about the late reply! We are a bit backlogged atm. I would suggest you trace down the OutOfMemory situation, it's likely the root cause. My best suggestion is to stress test your app while monitoring memory usage to see if you are doing anything wrong. Otherwise it may just be related to users using your app on a low-memory device? From our end it's tricky to get much further without more info unfortunately.
Closing due to inactivity.
How frequently does the bug occur?
Sometimes
Description
Noticing a weird crash log coming through crashlytics lately. There are 2 different stack traces coming from the same crash site / log on crashlytics. The most common being:
And occasionally:
I can not share a ton of internal code but the area that it appears to be crashing is during this block on the execute transaction line.
Mainly wondering what the vector crash could relate to, I have not been able to find much in searching for it. When looking for the out of memory crash I mainly see mentions of not closing realms properly. Recently I started using
toFlow
for observing changes and I believe I am closing the realms properly but that could be a possible issue. This is how I am doing that:Then in my viewModel
and my view model is scoped to fragment:
I know this is not a ton of information to work with and will be happy to provide additional details if I can.
Stacktrace & log output
No response
Can you reproduce the bug?
Not yet
Reproduction Steps
No response
Version
10.7.1
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
Many Android versions and devices
Build environment
Android Studio version: Android Studio Bumblebee | 2021.1.1 Patch 2 Android Build Tools version: 7.0.3 Gradle version: 7.0.2