httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39079] - thread eats 100% CPU, presumably spinning in futex
Date Mon, 27 Mar 2006 21:17:51 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39079>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39079





------- Additional Comments From rpluem@apache.org  2006-03-27 22:17 -------
First of all many thanks for the output. Whats currently confusing me is that
the thread that consumes the CPU is non of the ones that are in the same function.
Basicly I agree that it seems to be a dangerous thing to have two threads
working on the same data structures at the same time. This is waiting for an
accident to happen. I think this is caused by the fact that two threads use the
same worker (see worker at #4) This should not happen.
A similar problem was already discovered in PR#38793. Could you please check if
the patch attached to PR#38793 fixes your problem?


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message