perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Hay <steve....@uk.radan.com>
Subject Re: [RELEASE CANDIDATE] mod_perl 2.0-RC5
Date Tue, 12 Apr 2005 16:36:43 GMT
Geoffrey Young wrote:

>the mod_perl development team is pleased to announce that we have a new
>candidate for mod_perl 2.0, ready and waiting for testers.
>
No good for me on Win32 :(

Using Apache 2.0.53, bleadperl (@22511), I have the testsuite crashing 
the Apache.exe server every time in perl/ithreads_args.t.  Here's a 
stacktrace fwiw:

Perl_mg_free(interpreter * 0x06809098, sv * 0x110affc8) line 406 + 3 bytes
Perl_sv_clear(interpreter * 0x06809098, sv * 0x110affc8) line 5958 + 13 
bytes
Perl_sv_free2(interpreter * 0x06809098, sv * 0x110affc8) line 6191 + 13 
bytes
Perl_sv_free(interpreter * 0x06809098, sv * 0x110affc8) line 6171 + 13 bytes
Perl_ithread_create(interpreter * 0x04d942e8, sv * 0x00000000, char * 
0x090a2608, sv * 0x10722534, sv * 0x104213b4) line 476 + 13 bytes
XS_threads_new(interpreter * 0x04d942e8, cv * 0x08f13eb0) line 687 + 36 
bytes
Perl_pp_entersub(interpreter * 0x04d942e8) line 2816 + 16 bytes
Perl_runops_debug(interpreter * 0x04d942e8) line 1581 + 13 bytes
S_call_body(interpreter * 0x04d942e8, const op * 0x0adefd20, char 0) 
line 2211 + 13 bytes
Perl_call_sv(interpreter * 0x04d942e8, sv * 0x1042010c, long 4) line 
2143 + 15 bytes
modperl_callback(interpreter * 0x04d942e8, modperl_handler_t * 
0x0c3e31f8, apr_pool_t * 0x0c3dec88, request_rec * 0x0c3decc0, 
server_rec * 0x0029ce70, av * 0x10718e74) line 100 + 17 bytes
modperl_callback_run_handlers(int 6, int 4, request_rec * 0x0c3decc0, 
conn_rec * 0x00000000, server_rec * 0x0029ce70, apr_pool_t * 0x00000000, 
apr_pool_t * 0x00000000, apr_pool_t * 0x00000000, int 1) line 261 + 35 bytes
modperl_callback_per_dir(int 6, request_rec * 0x0c3decc0, int 1) line 
370 + 34 bytes
modperl_response_handler_run(request_rec * 0x0c3decc0, int 1) line 976 + 
13 bytes
modperl_response_handler(request_rec * 0x0c3decc0) line 1016 + 11 bytes
ap_run_handler(request_rec * 0x0c3decc0) line 153 + 78 bytes
ap_invoke_handler(request_rec * 0x0c3decc0) line 364 + 9 bytes
ap_process_request(request_rec * 0x0c3decc0) line 249 + 9 bytes
ap_process_http_connection(conn_rec * 0x00a6b4f8) line 251 + 9 bytes
ap_run_process_connection(conn_rec * 0x00a6b4f8) line 43 + 78 bytes
ap_process_connection(conn_rec * 0x00a6b4f8, void * 0x00a6b428) line 178
worker_main(long 1) line 730
_threadstartex(void * 0x0029d568) line 212 + 13 bytes
KERNEL

At this point, my Apache.exe process is a staggering 205 MB!!!

I'm using Perl's malloc here.  Randy, do you see the same with your 
ActivePerl (i.e. system malloc) setup?

Needless to say, the perl/ithreads_args.t test runs fine in isolation.  
Maybe we should drop this ithreads test from the distro too?

- Steve


------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are confidential
and intended for the addressee(s) only.  If you have received this message in error or there
are any problems, please notify the sender immediately.  The unauthorized use, disclosure,
copying or alteration of this message is strictly forbidden.  Note that any views or opinions
presented in this email are solely those of the author and do not necessarily represent those
of Radan Computational Ltd.  The recipient(s) of this message should check it and any attached
files for viruses: Radan Computational will accept no liability for any damage caused by any
virus transmitted by this email.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message