Smells quite similar to bug #1273478 - i.e. deadlock caused by holding a lock while waiting on the async network info operation to complete, and then the async operation tries to take the same lock
Smells quite similar to bug #1273478 - i.e. deadlock caused by holding a lock while waiting on the async network info operation to complete, and then the async operation tries to take the same lock