Closed sabergeek closed 6 years ago
SNAPSHOT 2.2.2 fixes https://github.com/realm/realm-java/issues/3629 which might fix this?
@Zhuinden I hope so! :) When is the release version of 2.2.2 expected to be out?
Personally, I'm surprised that it still isn't.
@sabergeek Can you verify that SNAPSHOT 2.2.2 works for you?
@kneth I certainly would, but I don't have access to those specific devices, nor emulators.
@sabergeek We will release a new version soon. I hope that you will have the time to upgrade your app and monitor Crashlytics to see if the crash still occurs.
@kneth I will push an update with Snapshot 2.2.2 and report back. Is there anything else I should be aware of/ expect with this snapshot (known bugs)?
@sabergeek it has less bugs than 2.2.1, and I do not know of any new bugs that were introduced.
You can either use the snapshot or wait a day (or two) to use a proper release.
@kneth Then I'll wait instead, and will report back soon :)
@sabergeek We have released 2.2.2 a few hours ago :-)
@kneth Seems to be alright! It's over a week now and no crashes yet.
@sabergeek Cool. I'll close the issue. Don't hesitate to reopen or create new issue if you see it again.
@kneth I am seeing the similar crash in crash reports on realm 2.2.2
Fatal Exception: io.realm.exceptions.RealmError: Unrecoverable error. Permission denied in /home/cc/repo/realm/realm-java-release/realm/realm-library/src/main/cpp/io_realm_internal_SharedRealm.cpp line 87 at io.realm.internal.SharedRealm.nativeGetSharedRealm(SourceFile) at io.realm.internal.SharedRealm.getInstance(SourceFile:208) at io.realm.internal.SharedRealm.getInstance(SourceFile:186) at io.realm.RealmCache.createRealmOrGetFromCache(SourceFile:124) at io.realm.Realm.getInstance(SourceFile:227)
@AamirAbro what directory are you trying to open the Realm in?
@Zhuinden the default one.
here is how am I creating the it.
Realm.init(Application.getContext()); RealmConfiguration configuration = new RealmConfiguration.Builder() .deleteRealmIfMigrationNeeded() .build();
Interesting, what device is it?
2.2.2 should have fixed it as per https://github.com/realm/realm-java/issues/3629
@Zhuinden Its happening mostly on HUAWEI devices.
Here is the distribution of users who git this crash after realm 2.2.2
update.
@AamirAbro do you open Realm instance in application.onCreate()
, or in Activity.onCreate()
?
in activity on create.
@beeender
any update, I have been seeing this crash alot. :(
@kneth @Zhuinden @AamirAbro Confirmed. I'm seeing the error again on 2.2.2 (Just found out 2.3.0 is out, does it fix this issue?) -
Unrecoverable error. Permission denied in /home/cc/repo/realm/realm-java-release/realm/realm-library/src/main/cpp/io_realm_internal_SharedRealm.cpp line 87
I also noticed the line number to which the log is pointing at is different this time. The log shared originally in this thread was pointing at 92 - This time at 87. Not sure if this will be helpful.
PS - I'm unable to re-open this issue since it seems like I don't have the privileges.
But what devices do you see this on?
@Zhuinden So far this was reported only on Lenovo A7010a48 - Android 6.0.
Hi!
We also have the same problem here. In Crashlitycs we have a crash:
Fatal Exception: io.realm.exceptions.RealmError: Unrecoverable error. Permission denied in /home/cc/repo/realm/realm-java-release/realm/realm-library/src/main/cpp/io_realm_internal_SharedRealm.cpp line 92
at io.realm.internal.SharedRealm.nativeGetSharedRealm(SharedRealm.java)
at io.realm.internal.SharedRealm.getInstance(SharedRealm.java:209)
at io.realm.internal.SharedRealm.getInstance(SharedRealm.java:186)
at io.realm.RealmCache.createRealmOrGetFromCache(RealmCache.java:124)
at io.realm.Realm.getDefaultInstance(Realm.java:209)
By now 100% of it are reported by HUAWEI GRA-L09 and 6.0 version.
And finally we are using 2.3.0 Realm version.
There are any news already? Do you need more information?
Thank you for your work.
@beeender @kneth do we have this HUAWEI device or should we order one for tests?
@sabergeek I have a Huawei device, would you please share your apk somewhere so I can verify it on my device first? Hope I can reproduce it .
I put in "On Hold" until @beeender has a chance to try to reproduce it.
@beeender I'll send it to you privately. Any email ID you can share?
@sabergeek Please send it to help@realm.io.
Hi all,
I am also getting this issue:
Permission denied in /home/cc/repo/realm/realm-java-release/realm/realm-library/src/main/cpp/io_realm_internal_SharedRealm.cpp line 87 Realm V 2.2.2
on
Lenovo S1a40 & HTC Desire 526GPLUS dual sim in Activity.onCreate()
@sabergeek @lkishor We have been unable to reproduce this bug. We need your assistance! @beeender has a Huawei device. If one of you can send us an apk that will enable us to see the problem we'd be eternally grateful.
@bmeike @kneth @beeender I just sent in a mail on help@realm.io with the details and a link to the APKs. Apologies for the delay! Do let me know if you need more info.
INTERNAL INFORMATION: https://secure.helpscout.net/conversation/318133134/8775/?folderId=539748
Cannot reproduce on Huawei Honor 7 :(
Some updates:
I try to reproduced this issue with devices in this issue on http://remote.testin.cn/machine/device/index , but no luck :(
https://code.google.com/p/android/issues/detail?id=8886 this Android issue seems to be related with this crash. But if that happens (context.getFilesDir()
returns null
), it should crash in SharedRealm.initialize()
when mkdir()
called first.
@SergiLlamasGuerrero can you please send your apk to us (help@realm.io) so i can try to reproduce it on HUAWEI GRA-L09 ?
Thank you @beeender for your help.
Our app is this one: https://play.google.com/store/apps/details?id=com.geomobile.tiendeo&hl=es And this is the information about this crash provided by Fabric: http://crashes.to/s/5797e3f66da
I hope this helps!
Sergi
@SergiLlamasGuerrero Still no luck to reproduce it on Huawei Honor 7 and Huawei P8 (which is almost the same device with GRA-L09) :(
I don't know if it will help but now the 84% of devices that crashed with this error are HUAWAI, and the 72% of HUAWAI that crashed are ALE-L21, followed by hi6210sft16 (16%) and then HUAWEI GRA-L09 (6%). However, this crash is not very common (130 crashes in a week from only 22 users and the app had 253.4k active users the same week).
Hope it could help a bit.
Thank you very much again!
Sergi
@SergiLlamasGuerrero When the crash happens, is it the first time the app open a Realm instance?
@beeender According to the data we have it seems that it is as you say
@SergiLlamasGuerrero Have you been able to repro this, or are you just seeing it in your Crashlytics reports? I am running Tiendeo on a Lenovo S1a40 Android 6.0, and have not seen it crash, yet.
We are seeing from 20-40 crashes on app a which has more then 300k users per day. 94% on Android 6 and 86% on Huawei devices.
@bmeike The information is what we have seen in Crashlytics, but we have not been able to reproduce the error either.
@AamirAbro Can you share you app with us? to help@realm.io if you want to share it privately. I can try my luck with a few Huawei devices i have. Also please let me know if there are any possible steps to reproduce the issue.
@AamirAbro Did you send us an APK which we can try?
@kneth sorry for delay, I have sent the build in email, @beeender You would have to login to app for this issue, it should crash as soon as you land on main screen after login. You can create an account if don't have one.
@AamirAbro Thanks. We'll take a look.
@AamirAbro The apk doesn't crash with our OPO, Huawei Hornor 7, Xiaomi Mi5. We will try to find more devices to try it.
Goal
Sharing a crash log (as reported by Crashlytics) on specific devices.
Expected Results
To verify if my current API usage is correct and hopefully find a resolution.
Actual Results
Code:
The RepoImpl instance is being created from two separate classes and the realm instance is being closed only when onDestroy() is triggered in each of the classes. clearRealm() is currently never called.
Realm version(s): 2.2.1
Android Studio version: 2.2.3
Which Android version and device: Samsung SM-A500F (Android 6.0) and Lenovo S1a40 (Android 4.4.4)
It's seemingly working well on other devices.