领域自行关闭答案

【问题标题】：Realm closes itself领域自行关闭
【发布时间】：2017-04-25 19:44:54
【问题描述】：

我在 Application 对象上使用一个静态全局 Realm 实例（从不关闭），仅用于 UI 线程，

@UiThread
public static Realm getRealm() {
    if (Thread.currentThread() == Looper.getMainLooper().getThread()) {
        return realmInstance;
    } else {
        Timber.e("Illegal access to getRealmObservable");
        throw new IllegalStateException("Only UI Thread can access this realm");
    }
}

以及 WorkerThread 的另一个单一用途领域如下：

@WorkerThread
public static void executeOnSingleUseRealm(final Realm.Transaction transaction) {
    if (Thread.currentThread() == Looper.getMainLooper().getThread()) {
        Timber.e("Wrong thread for Realm");
        throw new IllegalStateException("Wrong thread for Single use Realm");
    }

    Realm realm = null;
    try {
        realm = Realm.getDefaultInstance();
        realm.executeTransaction(transaction);
    } catch (Exception e) {
        Timber.e(e, "Exception in Single Use Realm transaction");
        throw e;
    } finally {
        if (realm != null) {
            realm.close();
        }
    }
}

但是我仍然看到使用单个全局 Realm 实例时崩溃：This Realm instance has already been closed, making it unusable.

我什至不知道这怎么可能。

这是我初始化 Realm 实例的方法：

应用程序创建

void onCreate(){
    ....
        Observable
            .fromCallable(() -> {
                Realm.init(SVApplication.this);
                RealmConfiguration realmConfiguration = new RealmConfiguration.Builder()
                        .deleteRealmIfMigrationNeeded()
                        .build();
                Realm.compactRealm(realmConfiguration);
                Realm.setDefaultConfiguration(realmConfiguration);
                return true;
            })
            .subscribeOn(Schedulers.io())
            .observeOn(AndroidSchedulers.mainThread())
            .subscribe((v) -> onRealmLoaded());
    }
}

void onRealmLoaded(){
    realmInstance = Realm.getDefaultInstance();
    ....
}

这是其中一项活动的崩溃之一：

void onStart(){
    ....    subscribeUntilDetach(realmInstance.where(Notification.class).findAllAsync().asObservable()
                        .onBackpressureLatest()
                        .switchIfEmpty(emptyNotification())
                        .map(notifications -> notifications.where().isNull("readTime").or().isEmpty("readTime").count())
                        .onBackpressureLatest()
                        .observeOn(AndroidSchedulers.mainThread())
                        .subscribe(count -> {
                            if (count == 0L) {
                                mNotificationBadge.setVisibility(View.GONE);
                            } else {
                                mNotificationBadge.setText(String.format(Locale.getDefault(), "%d", count));
                                mNotificationBadge.setVisibility(View.VISIBLE);
                            }
                        }, throwable -> Timber.e(throwable, "Error setting notification count")));
}

@Override
protected void onPause() {
    super.onPause();
    if (isFinishing()) {
        mCompositeSubscription.clear();
    }
}

protected void subscribeUntilDetach(@NonNull Subscription subscription) {
    mCompositeSubscription.add(subscription);
}

@Override
protected void onDestroy() {
    super.onDestroy();
    if (mCompositeSubscription.hasSubscriptions()) {
        mCompositeSubscription.unsubscribe();
    }
}

在某些活动中，此行也会因相同的错误而崩溃：

mCompositeSubscription.unsubscribe();

这是来自 Crashlytics 的堆栈跟踪，可能并不完全准确。

Fatal Exception: java.lang.RuntimeException: Unable to resume activity {com.myapp.mobile/com.teknoloji.myapp.ui.pages.HomeActivity}: rx.b.f: This Realm instance has already been closed, making it unusable.
   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3353)
   at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3384)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1443)
   at android.os.Handler.dispatchMessage(Handler.java:102)
   at android.os.Looper.loop(Looper.java:168)
   at android.app.ActivityThread.main(ActivityThread.java:5885)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)
Caused by rx.b.f: This Realm instance has already been closed, making it unusable.
   at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(Unknown Source)
   at rx.internal.util.InternalObservableUtils$ErrorNotImplementedAction.call(Unknown Source)
   at rx.internal.util.ActionSubscriber.onError(Unknown Source)
   at rx.observers.SafeSubscriber._onError(Unknown Source)
   at rx.observers.SafeSubscriber.onError(Unknown Source)
   at rx.exceptions.Exceptions.propagate(Unknown Source)
   at rx.observers.SafeSubscriber.onNext(Unknown Source)
   at rx.internal.producers.SingleProducer.request(Unknown Source)
   at rx.Subscriber.setProducer(Unknown Source)
   at rx.Subscriber.setProducer(Unknown Source)
   at rx.internal.operators.OperatorSingle$ParentSubscriber.onCompleted(Unknown Source)
   at rx.internal.operators.OperatorTake$1.onNext(Unknown Source)
   at rx.internal.operators.NotificationLite.next(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.accept(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.emitNext(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.emitFirst(Unknown Source)
   at rx.subjects.BehaviorSubject$1.call(Unknown Source)
   at rx.subjects.BehaviorSubject$1.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.Observable.create(Unknown Source)
   at rx.Observable.unsafeCreate(Unknown Source)
   at rx.Observable.create(Unknown Source)
   at com.teknoloji.myapp.ui.pages.HomeActivity.onStart(Unknown Source)
   at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1288)
   at android.app.Activity.performStart(Activity.java:6279)
   at android.app.Activity.performRestart(Activity.java:6325)
   at android.app.Activity.performResume(Activity.java:6330)
   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3336)
   at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3384)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1443)
   at android.os.Handler.dispatchMessage(Handler.java:102)
   at android.os.Looper.loop(Looper.java:168)
   at android.app.ActivityThread.main(ActivityThread.java:5885)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)
Caused by java.lang.IllegalStateException: This Realm instance has already been closed, making it unusable.
   at io.realm.BaseRealm.checkIfValid(Unknown Source)
   at io.realm.Realm.init(Unknown Source)
   at com.teknoloji.myapp.ui.pages.HomeActivity.lambda$onStart$3(Unknown Source)
   at com.teknoloji.myapp.ui.pages.HomeActivity$$Lambda$1.call(Unknown Source)
   at rx.internal.util.ActionSubscriber.onNext(Unknown Source)
   at rx.observers.SafeSubscriber.onNext(Unknown Source)
   at rx.internal.producers.SingleProducer.request(Unknown Source)
   at rx.Subscriber.setProducer(Unknown Source)
   at rx.Subscriber.setProducer(Unknown Source)
   at rx.internal.operators.OperatorSingle$ParentSubscriber.onCompleted(Unknown Source)
   at rx.internal.operators.OperatorTake$1.onNext(Unknown Source)
   at rx.internal.operators.NotificationLite.next(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.accept(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.emitNext(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager$SubjectObserver.emitFirst(Unknown Source)
   at rx.subjects.BehaviorSubject$1.call(Unknown Source)
   at rx.subjects.BehaviorSubject$1.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.subjects.SubjectSubscriptionManager.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.internal.operators.OnSubscribeLift.call(Unknown Source)
   at rx.Observable.create(Unknown Source)
   at rx.Observable.unsafeCreate(Unknown Source)
   at rx.Observable.create(Unknown Source)
   at com.teknoloji.myapp.ui.pages.HomeActivity.onStart(Unknown Source)
   at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1288)
   at android.app.Activity.performStart(Activity.java:6279)
   at android.app.Activity.performRestart(Activity.java:6325)
   at android.app.Activity.performResume(Activity.java:6330)
   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3336)
   at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3384)
   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1443)
   at android.os.Handler.dispatchMessage(Handler.java:102)
   at android.os.Looper.loop(Looper.java:168)
   at android.app.ActivityThread.main(ActivityThread.java:5885)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)

【问题讨论】：

你在项目的其他地方打电话给realm.close()吗？
@Fondesa 不，这是我关闭领域的唯一地方（我只为 WorkerThread 关闭）。 UI Realm 发生错误。
您是否仅在非 UI 线程上使用 executeOnSingleUseRealm()？注解@WorkerThread 仅被提示使用，不会强制其他线程使用。
我通过Thread.currentThread() == Looper.getMainLooper().getThread()检查当前线程。如果是 UI 线程，它应该抛出我的异常。
好吧，我的错。你能在这里发布用于初始化 UI 线程领域的共享实例的代码吗？

标签： android realm rx-java

【解决方案1】：

问题是：

已关闭的异常表明您正在尝试使用已关闭的境界，以一种不会被宣传为最佳的方式使用境界实践。 ...每个活动都应该有自己的领域实例以获得最佳性能。 ...在 onCreate() 创建一个领域实例，然后在 onDestory() 处销毁实例。 https://github.com/realm/realm-java/issues/2594#issuecomment-211793848

还有

...在类中保留 Realm 的静态字段不是一个好主意。建议将Realm的生命周期控制在Activity/Fragment/etchttps://realm.io/docs/java/latest/#controlling-the-lifecycle-of-realm-instances

因为在 Realm 中创建新实例，当至少有一个打开时，速度非常快，不要害怕创建多个 Realm 实例。

Realm 的一位高级软件工程师指出here：

只要您在调用 Realm.getInstance() 的线程上打开了至少一个实例，这只是一个 HashMap 查找...最佳实践是在您的线程存在期间保持 Realm 实例打开。

Realm documentation 中描述了最佳实践：

// Setup Realm in your Application
public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        Realm.init(this);
        RealmConfiguration realmConfiguration = new RealmConfiguration.Builder().build();
        Realm.setDefaultConfiguration(realmConfiguration);
    }
}

// onCreate()/onDestroy() overlap when switching between activities.
// Activity2.onCreate() will be called before Activity1.onDestroy()
// so the call to getDefaultInstance in Activity2 will be fast.
public class MyActivity extends Activity {
    private Realm realm;
    private RecyclerView recyclerView;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);

        realm = Realm.getDefaultInstance();
        // ...
    }

    @Override
    protected void onDestroy() {
        super.onDestroy();
        realm.close();
    }
}

对于工作线程，documentation recommends 在开始时获取 Realm 的新实例并在结束时关闭它。

protected Void doInBackground(Void... params) {
    Realm realm = Realm.getDefaultInstance();
    try {
        // ... Use the Realm instance ...
    } finally {
        realm.close();
    }

    return null;
}

【讨论】：

我已阅读文档。我不想遵循这种方法，因为第一次初始化需要时间。我把它放在后台线程中。由于后台初始化需要一些时间，onCreate 上的Realm.getDefaultInstance() 也失败了。我还从另一位高级工程师那里读到，为 UI 线程保留一个静态最终领域也很好。有些地方不对劲，但我的实现只是揭示了它。
是的，第一次初始化需要很短的时间，但只有在您启动应用程序时才会完成。我会遵循领域的指导方针，因为即使你让它工作了，将来也可能会出现其他问题。
我认为问题在于，您在工作线程中初始化 Realm。初始化完成后，您设置realmInstance。您正在访问onStart 中的realmInstance，这可能发生在realmInstance 初始化之前。当你在主线程上初始化realmInstance normal 时，问题是否仍然存在？
问题是，我没有关闭领域。但它会自行关闭。如果路由原因不固定，也会发生同样的情况。
不，不是，但我希望避免在主线程上初始化。

【解决方案2】：

我认为问题在于RealmObservableFactory。我已经删除了所有Rx + Realm 关系（.asObservable() 等），使用了老式的实现，并且进展顺利。

【讨论】：