Saying it worked in 4.0.4 was quite a valuable piece of information.  I can 
confirm now that memory_limit is broken in 4.0.6, I'll submit a fix to CVS 


At 15:23 28/6/2001, Swift wrote:
>Hi Zeev!
>Zeev Suraski wrote:
> > This isn't a known problem (well, at least I haven't heard any such
> > complaints).  It may be a coincidence (i.e. not related to 4.0.6) - I'd
> > wait and see if this problem persists.
>Thanks for your help. Ok, I will give it a try.
>But back to the first problem. You said that the memory_limit applies to 
>only ONE
>script (as I thought). You said that the problem may be somewhere else.
>But I got the described error-message without any load! I cutted our 
>before the tests and then only executed the 2 test-scripts. And in 10-20% 
>of the
>cases I got the error-message. BTW, our server has 512MB RAM and 90% free, 
>so RAM
>seems not to be the problem. The second strange thing is: With 4.0.4pl1 the
>memory_limit was 8M and with 4.0.6 I increased it to 16M. I never got the 
>with 4.0.4pl1 but with 4.0.6 nearly instantly (after a few minutes the 
>first time)!
>The two test-scripts only allocate 8MB each. When I execute only these two 
>and the server has no load besides of that and >400MB free RAM, and the 
>is 16M --- why will I get sometimes the out-of-memory warning? This 
>can't be, right!? Maybe this has something to do why the server crashed 
>  ... tobias wiersch from .de
>PHP Development Mailing List <>
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]

Zeev Suraski <[EMAIL PROTECTED]>
CTO &  co-founder, Zend Technologies Ltd.

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to