https://bz.apache.org/bugzilla/show_bug.cgi?id=61695
--- Comment #15 from Stefan Eissing <ste...@eissing.org> --- Jacob and Bernd: are you both talking about the same system? Otherwise I'd like to hear from Bern about the original issue and version 2.4.33. If yes: I see not how the process is stuck in these strack traces. It might be busy and there might be a bug causing this, but see no evidence of deadlocks or infinite loops. For example: the latest stacktraces show 2 threads: 1. a HTTP/1.1 request using mod_proxy 2. a HTTP/2 main connection that does a non-blocking read on a stream response Both manipulate list data structure and - unless memory is corrupted here - they cannot go into an infinite loop there. These locations might be visible in strack traces often, since both locations are I/O related and would be expected to show up on random traces. I have no good idea how to move forward on this, I must say. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
