php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #20795 Memory_limit not respected
Submitted: 2002-12-03 11:36 UTC Modified: 2002-12-20 01:00 UTC
Votes:2
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:2 (100.0%)
From: benoit dot delagarde at grecland dot com Assigned:
Status: No Feedback Package: Scripting Engine problem
PHP Version: 4.4CVS2002-12-03 OS: Windows XP Pro/BSDi/FreeBSD
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: benoit dot delagarde at grecland dot com
New email:
PHP Version: OS:

 

 [2002-12-03 11:36 UTC] benoit dot delagarde at grecland dot com 
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).

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-12-03 12:02 UTC] msopacua@php.net 
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.
 [2002-12-03 12:06 UTC] derick@php.net 
Please check (with phpinfo()) if the location of your php.ini file is correct (and watch the troubles with the file extensions in windows, the best thing to check if the file actually has the name 'php.ini' (and not 'php.ini.ini') is to check it in a DOS prompt.

Derick
 [2002-12-03 16:45 UTC] benoit dot delagarde at grecland dot com 
Oki, 
I have check (but i was sure):
Configuration File (php.ini) Path C:\WINDOWS\php.ini
And the file have the right name and the right location.

In all case, i suppose that normally, i should have a default value of memory_limit and max_execution_time displayed by phpinfo(). And it's not the case. 
(Note that this values are displayed under Linux with Apache/1.3.23, PHP Version 4.1.2)
 [2002-12-20 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over 2 weeks, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Apr 20 14:01:29 2024 UTC