Edit report at https://bugs.php.net/bug.php?id=72729&edit=1
ID: 72729
Updated by: requinix@php.net
Reported by: caaguado at xcentra dot com
Summary: php-cgi.exe/php_mbstring.dll crash Exception
0xc0000005 Fault offset 0x00026831
-Status: Open
+Status: Feedback
Type: Bug
Package: mbstring related
Operating System: Windows 10 64bit, Windows 7 64bi
PHP Version: 7.1.0beta1
Block user comment: N
Private report: N
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php
for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php
for Win32
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2016-08-01 19:01:57] caaguado at xcentra dot com
Description:
------------
php-cgi.exe crash with faulting module name php_mbstring.dll, Exception code: 0xc0000005, Fault
offset: 0x00026831
Excerpt from Windows Application Event Log:
===========================================
Level Date and Time Source Event ID Task Category
Error 2016-08-01 12:57:05 Application Error 1000 (100) "Faulting application name: php-cgi.exe,
version: 7.1.0.0, time stamp: 0x57901bea
Faulting module name: php_mbstring.dll, version: 7.1.0.0, time stamp: 0x5790217b
Exception code: 0xc0000005
Fault offset: 0x00026831
(...)
Faulting application path: S:\xtack\bin\p71\php-cgi.exe
Faulting module path: S:\xtack\bin\p71\ext\php_mbstring.dll
(...)
Error 2016-08-01 12:56:55 Application Error 1000 (100) "Faulting application name: php-cgi.exe,
version: 7.1.0.0, time stamp: 0x57901bea
Faulting module name: php_mbstring.dll, version: 7.1.0.0, time stamp: 0x5790217b
Exception code: 0xc0000005
Fault offset: 0x00026831
Problem reproduced on two differen systems and Windows 64-bit editions:
1) Hewlett-Packard HP EliteBook 8460p system with 2x Intel Core i5-2540M CPU @ 2.60GHz core(s), 8 GB
RAM and Microsoft Windows 7 Enterprise Multiprocessor Free SP1 64 bits version 6.1.7601
2) Apple Inc. MacBookAir6 2 system with 2x Intel Core i7-4650U CPU @ 1.70GHz core(s), 8 GB RAM and
Microsoft Windows 10 Pro Multiprocessor Free SP0 64 bits version 10.0.10586
The crash appears both in:
a) Apache 2.4.23 (Win32, VC14, Apache Lounge binaries, see http://www.apachelounge.com/download/). Classic CGI
interface used.
Apache shows the following entry ("trace8" trace level set) in its error logfile:
[Mon Aug 01 19:34:22.618493 2016] [cgi:error] [pid 5764:tid 2212] [client 127.0.0.1:49870] End of
script output before headers: php-cgi.exe
b) Nginx 1.11.2 (Win 32, official Nginx binaries for Windows, see http://nginx.org/en/download.html).
Nginx shows the following entry ("debug" trace level set) in its error logfile:
2016/08/01 20:03:42 [info] 2484#8068: *1 client prematurely closed connection, so upstream
connection is closed too while connecting to upstream, client: 127.0.0.1, server: localhost,
request: "GET /docs/phpinfo.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000",
host: "127.0.0.1"
Exactly the same HTTP server stacks (Apache 2.4.23 and Nginx 1.11.2) are used with PHP versions
7.0.9, 5.6.24 and 5.5.38, _WITHOUT_ the crash appearing.
Test script:
---------------
When starting up Apache 2.4.23 or Nginx 1.11.2, Windows shows a "CGI / FastCGI has stopped
working" popup twice (two crashes per HTTP startup attempt), resulting into the browser
ultimately receiving a "500 Internal Server" error from the HTTP server.
The fault is new to PHP 7.1.0beta1.
According to the PHP 7.1.0beta1 news.txt changelog, the only change in this release on mbstring is:
- Mbstring:
. Deprecated mb_ereg_replace() eval option. (Rouven WeÃling, cmb)
. Fixed bug #69151 (mb_ereg should reject ill-formed byte sequence).
(Masaki Kagaya)
Expected result:
----------------
Crash fixed and PHP 7.1.0x running flawlessly.
Actual result:
--------------
Please see attached logfiles, whose names should be pretty much self-explanatory. If that is not the
case, please kindly contact me back, so I can assist and provide as much info as needed. Thank you.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=72729&edit=1