[Twisted-Python] finding out what's blocking the reactor

Chris Withers chris at withers.org
Mon May 13 08:26:01 MDT 2019


Hi All,

On some busy instances of the app I'm working with/on, we see websocket 
connections being dropped due to not ping/ponging in time, I'm fairly 
sure this is as a result of some user-written callbacks blocking the 
reactor for long periods of time (seconds...).

What's the best way to debug a twisted application to find out what's 
blocking the reactor?

cheers,

Chris



More information about the Twisted-Python mailing list