java.util.concurrent.TimeoutException ..reported from clients which seems that the lock has reached limit to be locked

[google]

java.util.concurrent.TimeoutException ..reported from clients which seems that the lock has reached limit to be locked

[jpd236]

Thanks for your report. Unfortunately, I don't think it is an issue with Volley.

Per the stack trace, the app is hung on the following line of code:

if (buf == null || buf.length > mSizeLimit) {

which are trivial checks on buf/buf.length which should take nanoseconds, not seconds, to complete.

One of these possibilities thus seems likely, and none would be something we could do much about in Volley:

• The device is under heavy load to the point that trivial operations take tens of seconds (a strong possibility here, given that GC is running, is that the app which crashed has a memory leak).
• The phone happened to go to sleep at the wrong time; the timeout here is based on realtime, but if the app was doing lots of work in the background without holding a wakelock, it seems possible that it would go to sleep during the finalize() call and lead to a timeout when it woke up. (See some discussion).

I'm closing this without more info about the circumstances, but if you have a consistent way to reproduce this (ideally with sample code), or a full Android bugreport (taken through developer options) taken after a crash, we can take a closer look.