Getting ANR in ServiceWatcher in release builds with object-watcher-android artefact about leakcanary HOT 3 CLOSED

This is really surprising. ObjectWatcher.expectWeaklyReachable does have a lock but I don't see what could be talking so long, especially as the ANR seems to be stuck on computing the hashcode of a string that represents a UUID.

is there a way to disable and not install all watchers in the release build

Yes, you can do that in various ways:

• Pass the right (or empty) set of watchers to AppWatcher.manualInstall() (check the docs)
• Leverage the interface that ObjectWatcher implements: ReachabilityWatcher and then use a fake impl in release builds

If you want a no-op in prod, your best bet is to simply create an interface similar to ReachabilityWatcher, and in prod you have a no-op impl and you don't include the object-watcher dependency. In debug you include it and you have an impl that delegates to `ObjectWatcher.

from leakcanary.

I changed the impl to use a ConcurrentHashMap in 3.x so at least there won't be any locking in the future. Beyond that, I really have no idea what's happening here.

from leakcanary.

We are not able to reproduce it locally either. It seems there are always some really "strange" devices out there in the world :)

Thank you for the pointers on how to substitute a fake impl. I will try a simple upgrade to 3.0 version first though.

from leakcanary.