https://bz.apache.org/bugzilla/show_bug.cgi?id=64452
--- Comment #15 from Bernhard Friedreich <fries...@gmail.com> --- I can now reproduce the problem in my local vm with a more or less stock centos7 and our self compiled apache. Running gdb the interesting thing is that file_cleanup is reached for apr-tmp but never for modproxy.tmp. Sadly there seems to be a mismatch in line numbers to source - even if the same versions (apr 1.7.0 and apr-util 1.6.1) are used.. Breakpoint 1, ap_proxy_http_prefetch (url=<optimized out>, uri=0x7fffbc010d18, req=<optimized out>) at mod_proxy_http.c:807 807 rv = spool_reqbody_cl(req, &bytes); (gdb) Continuing. Breakpoint 2, apr_file_mktemp (fp=fp@entry=0x7fffe4a63958, template=0x7fffbc00ed80 "/tmp/apr-tmp.XXXXXX", flags=flags@entry=0, p=p@entry=0x7fffbc009f18) at file_io/unix/mktemp.c:177 177 { (gdb) c Continuing. Breakpoint 3, apr_unix_file_cleanup (thefile=0x7fffbc00ed98) at file_io/unix/open.c:80 80 rv = file_cleanup(file, 0); (gdb) c Continuing. Breakpoint 2, apr_file_mktemp (fp=fp@entry=0x7fffe4a63b30, template=0x7fffbc00ee50 "/tmp/modproxy.tmp.XXXXXX", flags=flags@entry=0, p=p@entry=0x7fffbc009f18) at file_io/unix/mktemp.c:177 177 { (gdb) c Continuing. -- 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