Edit report at https://bugs.php.net/bug.php?id=61577&edit=1
ID: 61577
Comment by: pirabid at gmail dot com
Reported by: uniflare at gmail dot com
Summary: php5ts.dll crashes when specific extensions are
loaded
Status: Assigned
Type: Bug
Package: Reproducible crash
Operating System: Windows7 Ultimate x86
PHP Version: 5.4.0
Assigned To: mattficken
Block user comment: N
Private report: N
New Comment:
I have the same problem on windows 7 (64-bit) using PHP 5.4.0
Apache crashes if I use the following two extension parallely:
extension=php_curl.dll
extension=php_gd2.dll
If I comment any one of these, Apache works okay.
Please fix this.
Previous Comments:
------------------------------------------------------------------------
[2012-05-04 14:56:50] zane at zanezane dot net
For me, problem is fixed since 5.4.1.
I tried seconds ago with 5.4.2 and is still ok.
------------------------------------------------------------------------
[2012-05-04 12:44:07] george dot gruber at emailourfamily dot com
A new note to this issue. I have updated PHP to 5.4.1 and Apache from
ApacheLounge to the 32-bit, openSSL 0.9.8v version and the problem still
exists. I was hoping the PHP 5.4.1 would resolve the issue.
------------------------------------------------------------------------
[2012-04-17 19:57:38] george dot gruber at emailourfamily dot com
I experiencing the same crash on two different Windows 7 Ultimate x64 machines.
Apache and PHP come up and run fine and occasionally I get the message in
error.log:
[mpm_winnt:notice] [pid 2200:tid 512] AH00428: Parent: child process exited
with status 255 -- Restarting.
At nearly the same time there are three entries in to the application event log
indicating the same error reported in bug:
Faulting application name: httpd.exe, version: 2.4.2.0, time stamp: 0x4f7ed6c4
Faulting module name: php5ts.dll, version: 5.4.0.0, time stamp: 0x4f4e7f05
Exception code: 0xc0000005
Fault offset: 0x0004c563
Faulting process id: 0x3870
Faulting application start time: 0x01cd1cb269ad9f3a
Faulting application path: C:\Apache24\bin\httpd.exe
Faulting module path: C:\PHP5\php5ts.dll
I have removed as many extensions as possible that still allows the system to
run properly. I had even gone as far as to remove php_mbstring and it didn't
change the results. Having removed some of the other extensions seem to reduce
it but this is not definitive. This is the list of what I had removed just for
reference:
php_gettext
php_ldap
php_pdo_mysql
php_pgsql
php_soap
php_sockets
php_tidy
php_xsl
I had verified that nothing required them although if that was the case you
would think that they wouldn't be doing anything to cause an error.
Interestingly enough as far as I can tell the pages are rendered properly and
that the only indication of any problem is the error.log (Apache) and Windows
events.
I am running PHP 5.4.0 and Apache 2.4.2 (ApacheLounge including
php5apache2_4.dll) and MySQL 5.6.5m8 on Windows 7 Ultimate x64 with SP1.
I have my own log file pertaining to processing of the pages and some functions
(MySQL requests are always captured) and I am trying to correlate the "crash"
to a particular event but so far nothing specific.
It is somewhat disconcerting and I do not know if there are any side issues
being created by this occurring. If anyone would like additional information
please let me know and I would be happy to submit it.
------------------------------------------------------------------------
[2012-04-15 12:34:16] paj...@php.net
no, it does not.
------------------------------------------------------------------------
[2012-04-15 12:29:17] o6asan at yahoo dot de
I have still the issue.
I feel that the number of crushes is increasing on my server.
I compared PHP5.4.0 to PHP5.4.0RC8. I found A difference in the configure
command options. Like this.
5.4.0
configure.js "--enable-snapshot-build" "--disable-isapi" "--enable-debug-pack"
"--disable-nsapi"
5.4.0RC8
configure.js "--enable-snapshot-build" "--disable-isapi" "--enable-debug-pack"
"--disable-isapi"
Does it have any effects on this issue?
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=61577
--
Edit this bug report at https://bugs.php.net/bug.php?id=61577&edit=1
