Bug #16060 Updated: Memory Access Violation

ID: 16060 Updated by: pthiebaud@labeltechnologies.com Reported By: pthiebaud@labeltechnologies.com Status: Open Bug Type: Reproducible crash Operating System: Windows 2000 PHP Version: 4.1.2 New Comment: After trying different configurations, it seems that the problem appears when using Zend Optimizer. I reinstalled PHP 4.12 and removed the option Zend Optimizer in the php.ini and it seems to work now. The solution works, but I definitely need to use the optimizer as I want to Zend Encode my pages. Previous Comments: ------------------------------------------------------------------------ [2002-03-15 03:54:03] pthiebaud@labeltechnologies.com The problem appears on any page. The only constant is that every page is connecting to a database (MS SQL Server) using DB::connect ------------------------------------------------------------------------ [2002-03-15 03:52:16] pthiebaud@labeltechnologies.com The problem appears on any page. The only constant is that every page is connecting to a database (MS SQL Server) using DB::connect ------------------------------------------------------------------------ [2002-03-14 17:27:30] ojacquet@terabit.be Just tried it with php 4.0.6 (allthough phpinfo() says 4.0.5) and everything works fine. btw it's Windows 2000 Server that I use. ------------------------------------------------------------------------ [2002-03-14 17:14:38] ojacquet@terabit.be I have the exact same configuration. I just installed PHP 4.1.2 to work with the ISAPI module. When I visit ANY php page it gives the following error msg: "Invalid access to memory location." The CGI module still works ok. I was looking for version 4.1.1 to test if this one works, but it is not available on php.net any more. Could someone provide me a link to 4.1.1, so that I can see if it works with that one. ------------------------------------------------------------------------ [2002-03-14 04:57:28] sander@php.net status -> feedback ------------------------------------------------------------------------ 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/16060 -- Edit this bug report at http://bugs.php.net/?id=16060&edit=1