ID: 20795 Updated by: [EMAIL PROTECTED] -Summary: Memory_limit and Max_execution_time not respected Reported By: [EMAIL PROTECTED] Status: Open Bug Type: *Configuration Issues -Operating System: Windows XP Pro +Operating System: Windows XP Pro/BSDi/FreeBSD -PHP Version: 4.2.3 +PHP Version: 4.4CVS2002-12-03 New Comment:
I know this is hard to believe, but the max_execution_time part is not a bug. See the NOTE at: http://www.php.net/set_time_limit The larger part of the execution is done by MySQL. max_execution_time, is the time that php keeps the processor busy - not the 'real' time. Leaving open for the memory_limit, which I reported myself not to be working in http://bugs.php.net/20738. I'll add any comments on that here. Updated summary and version. Previous Comments: ------------------------------------------------------------------------ [2002-12-03 11:36:21] [EMAIL PROTECTED] Hi i'm using Apache/1.3.26 (Win32) PHP/4.2.3, with mysql.exe Ver 11.18 Distrib 3.23.52, for Win95/Win98 (i32) 1) PhpInfo() don't give me the memory_limit that I set on default value. Non memory_limit appear on the page even though the php.ini file contain a definition. 2) PhpInfo() also don't give me the max_execution_time, witch is also setted. 3) When I execute an big sql query (20000 lines) (It was a mystake of course!!!) the memory grow up and grow up ... After more time than the max_execution_time, system blow up and apache is killed !!! I see in the task manager that memory in use by apache was up than 300Mo. And before the execution it was 5 or 6 Mo. 4) I will complete this report with the sql request made, but i notice that after stoping the html request mysqld-nt continue to work (100% of CPU_1) more than 10 minutes and apache also. I stop the daemon before they stop themself. I hope i was clear (im french and my english is poor). ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20795&edit=1
