DO NOT REPLY [Bug 39079] - thread eats 100% CPU, presumably spinning in futex

[bu...@apache.org]

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 Dick.Snippe@tech.omroep.nl  2006-05-03 21:10 -------
Today I tried apache-2.2.0
I haven't seen any hangs yet, but I collected ~20 coredumps in 10 hours.

All coredumps show more or less the same when doing "thread apply all bt",
viz:
* always ~64 threads (because ThreadsPerChild==64)

* many threads report a null pointer
Thread 3 (process 2636):
#0  0x00000216 in ?? ()
Cannot access memory at address 0x0

* others report all the same address (0x4067 in this case)
Thread 5 (process 2634):
#0  0x00000216 in ?? ()
Cannot access memory at address 0x4067

* thread 1 always reports
Thread 1 (process 2571):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e5b21b in __read_nocancel () from /lib/libpthread.so.0
#2  0x08083365 in ap_mpm_pod_check (pod=0x815e140) at pod.c:54
#3  0x0808161f in child_main (child_num_arg=0) at worker.c:1233
#4  0x08081774 in make_child (s=0x80a4f48, slot=0) at worker.c:1316
#5  0x080823b9 in ap_mpm_run (_pconf=0x80a30a8, plog=0x80d1160, s=0x80a4f48)
    at worker.c:1518
#6  0x08061c2c in main (argc=3, argv=0xbfe96574) at main.c:717

I'll try --enable-pool-debug and MALLOC_CHECK_=2
and see what happens...

-- 
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