我在 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 的另一个单一使用 Realm 如下:
@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();
....
}
这是其中一项 Activity 的崩溃之一:
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();
}
}
在某些 Activity 中,这条线也会因同样的错误而崩溃:
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)
最佳答案
问题是:
A closed exception indicates that you're attempting to use a closed realm, utilizing Realm in a way that would not be promoted as the best practice. ... Each activity is supposed to have its own realm instance for best performance. ... create a realm instance at onCreate() and destroy the instance at onDestory(). https://github.com/realm/realm-java/issues/2594#issuecomment-211793848
此外
...it is not a good idea that keep a static field of Realm in the class. It is recommended to control the Realm's life cycle within the Activity/Fragment/etc https://realm.io/docs/java/latest/#controlling-the-lifecycle-of-realm-instances
因为在 Realm 中创建新实例,当至少有一个打开时,速度非常快,不要害怕创建多个 Realm 实例。
Realm 的一位高级软件工程师指出 here :
As long as you have at least one instance open on a thread calling Realm.getInstance() it is just a HashMap lookup... Best practise is to keep the Realm instance open for as long as your thread lives.
最佳实践在 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;
}
关于android - Realm 自行关闭,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/43619625/
下面的代码在我第一次运行它时就可以正常工作:require'rubygems'require'spreadsheet'book=Spreadsheet.open'/Users/me/myruby/Mywks.xls'sheet=book.worksheet0row=sheet.row(1)putsrow[1]book.write'/Users/me/myruby/Mywks.xls'当我再次运行它时,我会收到更多消息,例如:/Library/Ruby/Gems/1.8/gems/spreadsheet-0.6.5.9/lib/spreadsheet/excel/reader.rb:11
最近因为项目需要,需要将Android手机系统自带的某个系统软件反编译并更改里面某个资源,并重新打包,签名生成新的自定义的apk,下面我来介绍一下我的实现过程。APK修改,分为以下几步:反编译解包,修改,重打包,修改签名等步骤。安卓apk修改准备工作1.系统配置好JavaJDK环境变量2.需要root权限的手机(针对系统自带apk,其他软件免root)3.Auto-Sign签名工具4.apktool工具安卓apk修改开始反编译本文拿Android系统里面的Settings.apk做demo,具体如何将apk获取出来在此就不过多介绍了,直接进入主题:按键win+R输入cmd,打开命令窗口,并将路
一段时间以来,我一直在使用open_uri下拉ftp路径作为数据源,但突然发现我几乎连续不断地收到“530抱歉,允许的最大客户端数(95)已经连接。”我不确定我的代码是否有问题,或者是否是其他人在访问服务器,不幸的是,我无法真正确定谁有问题。本质上,我正在读取FTPURI:defself.read_uri(uri)beginuri=open(uri).readuri=="Error"?nil:urirescueOpenURI::HTTPErrornilendend我猜我需要在这里添加一些额外的错误处理代码...我想确保我采取一切预防措施来关闭所有连接,这样我的连接就不是问题所在,但是我
我有一个super简单的脚本,它几乎包含了FayeWebSocketGitHub页面上用于处理关闭连接的内容:ws=Faye::WebSocket::Client.new(url,nil,:headers=>headers)ws.on:opendo|event|p[:open]#sendpingcommand#sendtestcommand#ws.send({command:'test'}.to_json)endws.on:messagedo|event|#hereistheentrypointfordatacomingfromtheserver.pJSON.parse(event.d
使用ruby的watir测试网络应用程序时,浏览器最后会保持打开状态。网上的一些建议是,要进行真正的单元测试,您应该在每次测试时(在拆卸调用中)打开和关闭浏览器,但这很慢而且毫无意义。或者他们做这样的事情:defself.suites=superdefs.afterClass#Closebrowserenddefs.run(*args)superafterClassendsend但这会导致摘要输出不再显示(诸如“100次测试、100次断言、0次失败、0次错误”之类的内容仍应显示)。我怎样才能让ruby或watir在我的测试结束时关闭浏览器? 最佳答案
我想设置秒数aflash在自动关闭之前向用户显示通知。 最佳答案 您可以在页面上使用一些简单的JavaScript(在此示例中使用jQuery):$('document').ready(function(){setTimeout(function(){$('#flash').slideUp();},3000);});假设保存您的flash消息的HTML元素的id是#flash,这将向上滑动并在3000毫秒(3秒)后将其隐藏。 关于ruby-on-rails-如何在一段时间后关闭Rails
在rails开发环境中,cache_classes是关闭的,所以你可以修改app/下的代码,不用重启服务器就可以看到变化。不过,在所有环境中,中间件只会创建一次。所以如果我有这样的中间件:classMyMiddlewaredefinitialize(app)@app=appenddefcall(env)env['model']=MyModel.firstendend我在config/environments/development.rb中执行此操作:config.cache_classes=false#thedefaultfordevelopmentconfig.middleware.
我有一个连接到服务器的rubytcpsocket客户端。在发送数据之前如何检查套接字是否已连接?我是否尝试“拯救”断开连接的tcpsocket,重新连接然后重新发送?如果是这样,有没有人有一个简单的代码示例,因为我不知道从哪里开始:(我很自豪我设法在rails中获得了一个持久连接的客户端tcpsocket。然后服务器决定杀死客户端,一切都崩溃了;)编辑我已经使用此代码解决了一些问题-如果未连接,它将尝试重新连接,但如果服务器已关闭则不会处理这种情况(它将继续重试)。这是正确方法的开始吗?谢谢defself.write(data)begin@@my_connection.write(
我有一个用Rails3编写的站点。我的帖子模型有一个名为“内容”的文本列。在帖子面板中,html表单使用tinymce将“content”列设置为textarea字段。在首页,因为使用了tinymce,post.html.erb的代码需要用这样的原始方法来实现。.好的,现在如果我关闭浏览器javascript,这个文本区域可以在没有tinymce的情况下输入,也许用户会输入任何xss,比如alert('xss');.我的前台会显示那个警告框。我尝试sanitize(@post.content)在posts_controller中,但sanitize方法将相互过滤tinymce样式。例如
我正在将一些遗留的Watir脚本迁移到Watir-Webdriver。除了他们如何设计Watir-Webdriver来处理弹出窗口之外,迁移大部分进行得很顺利。他们没有使用久经考验的“附加”方法,而是用简化的“窗口”方法取而代之。语法非常简单,但是我很难理解如何在不关闭父窗口的情况下关闭单独的子窗口。目前我的代码是这样的-b.button(:xpath=>PREVIEWBUTTON).clickb.window(:title,POPUPWINDOW).useDOb.closeend目前正在发生的是b.close方法正在关闭子窗口和父窗口。我不确定为什么会这样,因为b.close方法包含