Community
Participate
Working Groups
Created attachment 183703 [details] patch We've been seeing a deadlock in an adopter produce caused by the StructuredTextEditor's busy state ending. The deadlock is caused when the TimeOutExpired TimerTask attempts to execute the runnable in the UI thread. Once the runnable executes, it attempts to cancel the timer in endBusyStateInternal(). The problem is that if the Timer owns a lock that is also required by Timer#cancel(), we'll get a deadlock since the runnable is being executed in a different thread.
Changes checked in.