Running ATS in forward transparent mode with Http/2 support enabled. After a few page views, ATS gets into a state where it is consistently using more than 100% CPU. I think what is happening is that the origin server is closing the connection (we get a TS_EVENT_VCONN_EOS in FetchSM). FetchSM sends a BODY_DONE to Http2ClientSession but the http_vc (origin socket?) is never closed, so with each poll interval the EOS is reported again and again.