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 Thu, 04 May 2006 08:52:55 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 Dick.Snippe@tech.omroep.nl  2006-05-04 08:52 -------
(In reply to comment #18)
> I'll try --enable-pool-debug and MALLOC_CHECK_=2
> and see what happens...

I'v got one instance running with --enable-pool-debug, Unfortunately when it
dumped core, it also garbled the error log. There's a hole in the error log, and
a garbled line:
[Thu May 04 10:20:06 2006] [info] mem_cache: Cached url:
http://beeldbank.schooltv.nl:80/peuterskleuters/mmbase/attachments/4591?
apr_table_addn: key not in ancestor pool of t
[Thu May 04 10:27:25 2006] [info] removed PID file /e/fp/teleac/log/httpd2.pid
(pid=12045)
[Thu May 04 10:27:25 2006] [notice] caught SIGTERM, shutting down
[Thu May 04 10:27:50 2006] [notice] Apache/2.2.2 (Unix) configured -- resuming
normal operations

The stack trace from the coredump is more or less the same: many threads without
a stacktrace:
Thread 7 (process 17594):
#0  0x00000202 in ?? ()
Cannot access memory at address 0x702f6e69

Thread 6 (process 17595):
#0  0x00000246 in ?? ()
Cannot access memory at address 0x0

only thread1 has a stacktrace:
Thread 1 (process 17533):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e9721b in __read_nocancel () from /lib/libpthread.so.0
#2  0x08083521 in ap_mpm_pod_check (pod=0x816a340) at pod.c:54
#3  0x080817c7 in child_main (child_num_arg=0) at worker.c:1233
#4  0x0808191c in make_child (s=0x8168b20, slot=0) at worker.c:1316
#5  0x080819bb in startup_children (number_to_start=1) at worker.c:1350
#6  0x08082133 in ap_mpm_run (_pconf=0x809d778, plog=0x80a68c0, s=0x8168b20)
    at worker.c:1612
#7  0x08061e04 in main (argc=3, argv=0xbfbd1f74) at main.c:717

I'll try to catch another coredump.

Another instance is running with MALLOC_CHECK_=2, this instance reports
[Thu May 04 00:34:21 2006] [notice] child pid 12514 exit signal Segmentation fau
lt (11), possible coredump in /e/fp/shrd01/tmp

(mind you: a Segmentation fault and not Aborted, so MALLOC_CHECK_=2 didn't do
anything in this case, i.e. the corruption might not be malloc related)

The stacktrace is the same
Thread 4 (process 13082):
#0  0x00000206 in ?? ()
Cannot access memory at address 0x0

Thread 3 (process 13083):
#0  0x00000206 in ?? ()
Cannot access memory at address 0x4067

Thread 2 (process 13084):
#0  0x00000293 in ?? ()
Cannot access memory at address 0x4067

Thread 1 (process 13018):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ead21b in __read_nocancel () from /lib/libpthread.so.0
#2  0x08083365 in ap_mpm_pod_check (pod=0x80c0bb8) 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=0xbffe82d4) at main.c:717


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