Crash CursorWindow.java - Could not allocate CursorWindow about android-client

[chillaq]

Thanks @DevHilmi , I see a pull request for this issue, we will review it and get back to you.

[NicoZelaya]

Hi @DevHilmi !

Sorry to hear of your inconveniences. We tried different scenarios on few devices with very high amounts of Splits (22k+) stored in the DB, with and without dynamic configs and we couldn't repro this particular failure.
We do get some messages that are similar but none of them was a Fatal/crash and the applications recovered by themselves, with or without the transaction code.

Nevertheless, as you pointed out that query could return a big result so using @transaction seems like the right thing to do. We've released an RC where we merged your PR that you can try if you want, with version 2.6.9-rc1. Since we couldn't repro we can't say for certain it'll fix your problem but it would be great if you can give it a try and let us know, if it fixes the issue we'll release as a stable patch.

If you could share some more details around where are you instantiating the SDK factories (on a lifecycle hook, main thread or background thread) as well as the code/configs used, when and how are you destroying it if that's the case, and which other libraries and versions you have installed, it would be amazing. You can share this here or through [email protected] if that's best.
We'll try to replicate your environment to see if we can also repro to confirm the fix. If you prefer to do it over zoom, please reach out through [email protected] so we schedule one.

Again, my sincere apologies for the inconveniences, we're working to try and figure out why you're getting issues with the SQLite DB as our top priority in mobile.

Best regards,
Nicolas.

[DevHilmi]

Hi @NicoZelaya

Thank you for the detailed explanation for this issue and RC Release.

For the @transaction improvement we already try it out in our project but the issue is still happening.

For details "instantiating the SDK factories (on a lifecycle hook, main thread or background thread) as well as the code/configs used, when and how are you destroying it if that's the case, and which other libraries and versions you have installed". I will consult our Internal team to provide that through email.

[dstyo]

Hi @NicoZelaya

This issue still exists even though we have used @transaction. This issue only appears on os 10. I want to ask which version of androidTargetSdkVersion and androidCompileSdkVersion does this split use? and what version of room for this split? is it using the target API and compile 29? If so, should we add <application android: requestLegacyExternalStorage = "true" ...> for android Q https://medium.com/@sriramaripirala/android-10-open-failed-eacces-permission-denied-da8b630a89df?

[NicoZelaya]

Hi @dstyo!

Currently we have the following setup in the SDK:

• compileSdkVersion: 28
• minSdkVersion: 15
• targetSdkVersion: 28
• Room version: '2.2.2'

But in the app we're using to run our automated tests, we override the targetSdkVersion with 29 and Room '2.2.5'.

I think this is not access related, but you're definitely welcome to try and see if that tag solves the problem for you. Sadly, given we couldn't repro properly yet, we can't say for certain either it'll help or not.

Thank you for sharing it anyways! Really appreciated, any extra detail you could have to help us reproduce the issue would be amazing.

Best,
Nico.

[chillaq]

Hi Dwi, We released Android SDK 2.6.9 to fix this issue.

Thanks
Bilal

[dstyo]

Thanks Bilal will upgrade into Android SDK 2.6.9 today , thank you split team.