PHP 4.0 Bug #6229: Access violation after php.exe execution is complete
| From: | chris-php-bugs at digitaria dot com | Date: | Fri, 18 Aug 2000 00:32:59 +0000 |
| Subject: | PHP 4.0 Bug #6229: Access violation after php.exe execution is complete | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-29370@lists.php.net to get a copy of this message | ||
From: chris-php-bugs@digitaria.com
Operating system: Windows 2000 SP1
PHP version: 4.0.1pl2
PHP Bug Type: Reproduceable crash
Bug description: Access violation after php.exe execution is complete
There appears to be some sort of library conflict with 4.0.1pl2 and Windows 2000 (running as a CGI).
I get errors like those below every time php.exe executes:
Application popup: php.exe - Application Error : The instruction at "0x77fca8ac"
referenced memory at "0x00080101". The memory could not be "written".
(The instruction address here may vary by about 16 bytes; the memory address has always been
0x00080101 or 0x00080100)
Application popup: php.exe - Application Error : The instruction at "0x77fca9ea"
referenced memory at "0x00000010". The memory could not be "read".
The requests are in fact processed correctly and there is no trace of a message in the PHP error
logs. Before applying Service Pack 1, there was a good chance (5-50%) that a CGI error ("FATAL:
erealloc(): Unable to allocate (a number between 15 and 30K) bytes") would be sent to the
browser. Post Service Pack 1, I have yet to see the CGI error but the application error log message
is generated for each request.
Our client should be moving to a Linux/Apache setup within 2 weeks but I think it'd be a good
idea to investigate W2k stability in any case. I can provide pcAnywhere access to the remote server
to a trusted individual.