Closed hanspeide closed 8 years ago
Hi! It doesn't look like a Realm issue
public ProxyState(Class<? extends RealmModel> clazzName, E model) {
this.clazzName = clazzName;
this.model = model;
}
Here is the implementation of ProxyState
and you can see it is quite a simple function. I am not quit sure why would this happen, but it seems other things are not correct than Realm. Can you share the full log with other threads backtrace as well?
Thanks for looking into it. Here's a gist with the full backtrace.
It claims the GC blocked it with an ANR, while you were iterating a result set.
at no.urbaninfrastructure.bysykkel.supervisor.ui.map.SupervisorMapPresenter.renderStationMarkers(SupervisorMapPresenter.java:143)
This SupervisorMapPresenter
could be interesting.
GC thread is holding a lock held mutexes= "JdwpNetStateBase lock"
i think it is blocking the main thread. But not sure why...
Looks like this indeed is a lock occurring somewhere else, and is not related to Realm. Closing. Thanks for taking time to look into it.
I have an app that never sleeps, with the screen always on. When I leave it on overnight I find it unresponsive in the morning, and when touching the screen it is eventually killed with an ANR. The only thing in traces.txt that points to my app also points to Realm, though I'm by know means certain that this is a Realm issue.
Expected Results
App is responsive.
Actual Results
App is unresponsive, and is eventually killed with ANR being the cause.
In traces.txt I see this:
Steps & Code to Reproduce
Exact steps unknown. I've left the app open during the night, and find it unresponsive in the morning. Line 59 in StationAvailabilityRealmProxy.java is
this.proxyState = new ProxyState(no.urbaninfrastructure.bysykkel.supervisor.domain.StationAvailability.class, this);
Version of Realm and tooling
Realm version: 2.0.2
Android Studio version: 2.2
Which Android version and device: 5.1.1, Lenovo Yoga Tab 2 (YT3-X50L)