Edit report at https://bugs.php.net/bug.php?id=61577&edit=1

 ID:                 61577
 Comment by:         o6asan at yahoo dot de
 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 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?


Previous Comments:
------------------------------------------------------------------------
[2012-04-12 19:55:43] uniflare at gmail dot com

@pajoye at php dotnet

REVELATION: Please see below, I seem to have solved my problem;
===========================
Ill explain what you asked for anyway.

Tried these configurations (all other extensions disabled, default php.ini).
-- 1
;extension=php_mbstring.dll
extension=php_bz2.dll
extension=php_gd2.dll

-- 2
extension=php_mbstring.dll
;extension=php_bz2.dll
extension=php_gd2.dll

-- 3
extension=php_mbstring.dll
extension=php_bz2.dll
;extension=php_gd2.dll.

These above all work fine.
----------
But this does not work in 5.4.0:

extension=php_mbstring.dll
extension=php_bz2.dll
extension=php_gd2.dll
-----------
DLL Versions--
Default ext files from 
http://windows.php.net/downloads/releases/php-5.4.0-Win32-VC9-x86.zip
File versions all report: 5.4.0.0 / Mod@ 29/02/12 19:39
===========================
Note;

Using the RC8 Version I have done some more testing and it appears there is 
something happening once php has parsed the file.
I have this code in a file:

<?php phpinfo(); ?>

If I stop the browser from continuing to load the page it gives me the entire 
phpinfo output with the 3 modules apparently enabled. 
Although event viewer still reports a crash.

Apache error log has nothing about this error, neither does php error log 
(php_startup etc variables enabled ofc).
===========================
Revelation!?;

Now back with 5.4.0 Official, re-ran phpinfo.php with all 3 ext enabled and now 
it shows the page properly with NO CRASH.... Strangely fixed!?

All versions now working;
Apache 2.4.1/Apache2.2.17 + PHP 5.4.0/PHP 5.3.10
----------------
Following Ext enabled on working 5.4.0 Offical:

extension=php_mbstring.dll
extension=php_bz2.dll
extension=php_gd2.dll
extension=php_curl.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_sqlite3.dll
extension=php_fileinfo.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_pdo_mysql.dll
extension=php_pdo_sqlite.dll
extension=php_sockets.dll
extension=php_tidy.dll
extension=php_xmlrpc.dll
extension=php_exif.dll

Only the 3 ext causing issues were enabled in RC8 dir.

This is extremely puzzling. Steps I took while testing:
Replace the official 5.4.0 dir with the RC8 5.4.0 dir, 
Restart and test error several times trying to stop processing of phpinfo page 
long enough to look. 
Re-replace 5.4.0RC8 dir to Official. 
Re-Test.. no Crash.. Fixed?
===========================
Testing RC8 Again..
phpinfo page loads and crashes once loaded. Everytime. (5/5).

Official Once again..
Everything works fine...

===========================

This leads me to believe RC8 has had some part in this.
Perhaps a remnant dynamic configuration with apache.
For now, I appear to have solved my problem. But I do
still believe there is some inherent instability with 
these 3 extensions even in the official build.

Thanks

------------------------------------------------------------------------
[2012-04-12 17:56:09] paj...@php.net

You said "I removed some and it works", or something along this line... 

@matt, please follow that further. As in, load this 3 DLLs with the given 
versions 
and see if it works in the same configuration.

------------------------------------------------------------------------
[2012-04-12 17:20:10] uniflare at gmail dot com

@pajoye at php dot net

Are you unable to read the original bug report or something, the dll files in 
question were mentioned in the description...

This should be looked into, it means you cannot use mbstring, curl and GD2 at 
the same time, which is not good at all. They all serve a very useful purpose.
There is obviously some compatibility issue with these dll's.

If you cannot read the original bug report, then here;

php_mbstring.dll
php_gd2.dll
php_curl.dll

--
This is using a default setup as explained above on a system more than capable.
And trust me, I am by far no beginner in using PHP, compiling my own versions 
with custom extensions etc. Trust me when i say, this should not be happening.

PHP5.3.10 has NO problems using all 3 extensions.
only PHP 5.4.0.

Thanks.

------------------------------------------------------------------------
[2012-04-12 16:55:54] jmquarck at gmail dot com

Using Windows 7 Ultimate 64 bits with PHP 5.4 and Apache 2.4 or Apache 2.2

http://localhost     OK

http://localhost/phpinfo.php    crashes and changes url to 
www.localhost.com/phpinfo.php

It happens even if mbstring, curl and g2 extensions are disabled.

------------------------------------------------------------------------
[2012-04-12 15:07:13] paj...@php.net

@uniflare at gmail dot com

Tell me which DLLs you are referring to.

Without that, there is zero chance that I can even remotely going to test it.

------------------------------------------------------------------------


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

Reply via email to