ID: 37300 User updated by: astinky at lycos dot com Reported By: astinky at lycos dot com Status: Open Bug Type: Feature/Change Request Operating System: Windows Server 2003 PHP Version: 5.1.3 New Comment:
Sorry, I missed your last comment before my last post. I will indeed give that snapshot a try and report back as soon as I get it tested! Previous Comments: ------------------------------------------------------------------------ [2006-05-11 14:02:00] astinky at lycos dot com Perhaps whatever Dmitry did here: http://bugs.php.net/bug.php?id=36568 Changed memory use on windows, without actually enabling the memry limit I assume that the intention is that there should be no memory limit at all on windows? If that is the case, then there is one now, I just can't change it. I know my script is not using the entire 1GB of system ram on this server (12 MB maybe...). When my script stopped working corresponds to the time of the change in bug ID 36568. I'd rather not rollback to php 5.0.5 or have to compile 5.1.4 myself but ultimately I'll have to if the old behaviour is not restrored or the memory limit fully enabled. I'm not meaning to nag here, just filling in more info that I hope will be helpful. I'll find a solution one way or another but it is my hope that the old behaviour of memory use on windows will be restored or the memory limit will be fully enabled, whatever you guys think is appropriate. ------------------------------------------------------------------------ [2006-05-11 13:55:32] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip Default php does not have any memory limit. Please use php5handler2_2.dll if you're using apache 2.2 ------------------------------------------------------------------------ [2006-05-11 13:49:25] astinky at lycos dot com Ah, thanks. The thing is, this memory intensive script of mine worked fine on php 5.0.5, but its output is truncated on php 5.1.2 and up. It generates no other errors. As well, our upload scripts used to allow a 40 MB file upload on php 5.0.5 and previous versions. I have not tested whether it still does, but I assume it is affected by the changes in memory limit behaviour on windows. Something else has changed with respect to memory use on windows. Perhaps the harcoded memory limit of php has been reduced? If I build 5.1.4 for Win32 from source myself can I enable the memory limit or change the hardcoded limit? (I suspect from your comment I can) Thanks again for your attention to this matter, it is much appreciated. ------------------------------------------------------------------------ [2006-05-11 10:51:23] [EMAIL PROTECTED] Windows builds ship without memory limit feature. This was done on purpose. I have changed the category to change request since we might consider changing it. ------------------------------------------------------------------------ [2006-05-11 10:10:40] astinky at lycos dot com Additional info/correction: Actually the weserver would fault on shutdown with Apache 2.2.0 - php 5.1.2 (and 5.1.3) if the hardcoded memory limit was exceeded. With Apache 2.2.2 - php 5.1.3 (and 5.1.4) the webserver will fault at the time the memory limit is exceeded. The IIS system mentioned above is running php as an ISAPI. I usually set the memory limit in the php.ini anyway, not in the script. Still it has no effect. If only the fgetcsv function was not so hard on resources I would not be having this issue. I could solve my problem by converting the tab delimited text file I am reading into a MySQL table, but I'd really like to just be able to read the text file in the script so it is more portable. The problem persists in php 5.1.4. I compared the zend_alloc.c of php 5.0.5 to php 5.1.4 and found some suspicious differences, but nothing I could say for sure is responsible. Just let me know if there is any other info I can provide that may help. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/37300 -- Edit this bug report at http://bugs.php.net/?id=37300&edit=1
