Status Update
No update yet.
Comments
da...@google.com
This is occurring due to the usage of the BundledSQLiteDriver that loads a native file (JNI).
A small workaround you can try is to create a wrapper driver that initializes the actual one later when a connection is being opened in a background thread, delaying the initialization of the JNI library:
class BundledSQLiteDriverWrapper : SQLiteDriver {
private val actual by lazy {
BundledSQLiteDriver()
}
override fun open(fileName: String): SQLiteConnection {
return actual.open(fileName)
}
}
m....@gmail.com
hey , Do I really have to do that ? . It is not hurting my application at all . I was just taking some clarity on to why it is occurring which you provided.
Just dont want to run into any problems in the future since we just freshly started working with Room KMP .
Please do let me know if I should attempt a solution like you have provided or if its fine the way it is .
da...@google.com
If you don't perceive the disk read as an issue during startup / database initialization then you don't have to do the workaround. I provided it in the mean time if it was hurting your app while we try to make a fix.
m....@gmail.com
Great ! .acknowledged. Ty
da...@google.com
da...@google.com
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Daniel Santiago Rivera <
Link:
Lazily load SQLite's native library when a connection is opened.
Expand for full commit details
Lazily load SQLite's native library when a connection is opened.
Moving the load call into an inner object effectively makes it so that the library is loaded lazily when the object's class is loaded, i.e. when instantiated and accessed during the open call.
Bug: 363985585
Test: BundledSQLiteDriverTest.kt
Change-Id: I72fa01618169cb3225ea9d5d5e9f9ae59c6d4b09
Files:
- M
sqlite/integration-tests/driver-conformance-test/src/androidInstrumentedTest/kotlin/androidx/sqlite/driver/test/BundledSQLiteDriverTest.kt - M
sqlite/sqlite-bundled/src/jvmAndroidMain/kotlin/androidx/sqlite/driver/bundled/BundledSQLiteDriver.jvmAndroid.kt
Hash: 4f69d19088dae47b6a7bcf454ea22f7e2da78e92
Date: Tue Jan 21 17:51:32 2025
da...@google.com
na...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.sqlite:sqlite-bundled:2.5.0-alpha13androidx.sqlite:sqlite-bundled-android:2.5.0-alpha13androidx.sqlite:sqlite-bundled-iosarm64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-iossimulatorarm64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-iosx64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-jvm:2.5.0-alpha13androidx.sqlite:sqlite-bundled-linuxarm64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-linuxx64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-macosarm64:2.5.0-alpha13androidx.sqlite:sqlite-bundled-macosx64:2.5.0-alpha13
Description
Following the steps outlined in the official KMP Room docs (https://developer.android.com/kotlin/multiplatform/room ) , I see 5 strict mode violations in my code.
They dont seem to cause any noticable lag but i was wondering if this violation is expected?