This looks like a bug that was fixed shortly after the 2.4.17 release.
When the client resets a HTTP/2 stream (request) before the server
has started submitting a response, mod_http2 trips and this may
lead to a crash later, as you observed.
See http://svn.apache.org/viewvc?view=revision&revision
Hello!
Using 2.4.17.
There seem to be an issue with http/2:
I have these in the vhost error log:
[Tue Oct 20 12:00:35.797584 2015] [http2:warn] [pid 21608:tid
113684011906816] (70015)Could not find specified socket in poll list.:
[client x.x.x.x:65519] AH02953: h2_mplx(139): stream for response
