#27713 [Bgs]: PHP has encountered an Access Violation at 0101A8B4

ID: 27713 User updated by: thierry dot bo at netcourrier dot com Reported By: thierry dot bo at netcourrier dot com Status: Bogus Bug Type: Unknown/Other Function Operating System: Win32 2000 PHP Version: 5.0.0RC1 New Comment: Yes, but I think of some memory leak, and I believe the violation address could be useful, you could cross this information with other bugs, but maybe not. By the way I just switched to php-cgi-exe and there is no php crash. Previous Comments: ------------------------------------------------------------------------ [2004-03-26 11:04:09] derick@php.net If it's not reproducable, how can we fix it? ------------------------------------------------------------------------ [2004-03-26 08:23:21] thierry dot bo at netcourrier dot com Description: ------------ Sorry, but this bug is not reproducible. Switching from an application that runs fine with PHP4 to PHP5ISAPI with IIS5, refreshing the main page raise "PHP has encountered an Access Violation at 0101A8B4" 9 times out of 10 (just hitting refresh from my browser). The application does not use classes, exept the database abstraction layer that use PEAR MDB latest CVS, but maybe that can be in PEAR destructors called when the script reach the last line. What I tried is typing exit() function from the top of the runned script, hitting refresh several times. What I saw is that the error occurs only at the end of the script (I mean, inside the last 75 lines), the more close I am from the last lone, the more often the error occurs. The only thing that is constant is the error message, it is always the same. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27713&edit=1