that to
include my sapi module --with-capi.
If someone could give me a reference to SAPI documentation (none of which I
could find), or give me a lead on what my problem might be, I'd appreciate
it.
My SAPI code can be had at
http://www.ashpool.com/dist/php4-capi-v200-p1.tar.gz
--
Alex Leigh
PROTECTED] wrote:
Are you calling request_shutdown?
Also, are you sure it's actually leaking? Does it leak 200-400KB on each
and every request, or does this rate 'slow down' at some point?
Zeev
At 18:20 21/12/2001, Alex Leigh wrote:
All -
I have written a SAPI module for a new webserver
an
explicit cleanup handler for the threads, if that makes any difference; they
are exiting normally by returning off the function called in
pthread_create().
Does this web server spawn a new thread for each request? Or does it reuse
its threads?
Andi
At 12:22 PM 12/21/2001 -0600, Alex Leigh wrote
:52 PM, Andi Gutmans [EMAIL PROTECTED] wrote:
Check out DllMain() in php4isapi.c.
Are you running the thread attach and thread detach code?
Andi
At 12:43 PM 12/21/2001 -0600, Alex Leigh wrote:
It can do both. In the testing configuration, it is not pooling but
destroying the threads
:
The way TSRM is written is not designed for servers that don't reuse
threads for more than one request, so if that's how it works - you're going
to see a growing memory image all the time :I
At 22:16 21/12/2001, Alex Leigh wrote:
Ok. I looked at the ISAPI code, and I am now calling
It sounds like there was a particular reason for writing it this way ?
I am considering what effect it will have on me if I simply require that
people use thread pooling, and I'm going to do some tests to see whether
there's still a leak condition or if it stabilizes when I reuse them.
Alex
On
