Bug #61744 [Com]: preg_match crashes
| From: | bugzilla33 at gmail dot com | Date: | Mon, 16 Apr 2012 16:53:59 +0000 |
| Subject: | Bug #61744 [Com]: preg_match crashes | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-169639@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=61744&edit=1
ID: 61744
Comment by: bugzilla33 at gmail dot com
Reported by: bugzilla33 at gmail dot com
Summary: preg_match crashes
Status: Open
Type: Bug
Package: *Regular Expressions
Operating System: Win 7 64-bit
PHP Version: 5.4.1RC2
Block user comment: N
Private report: N
New Comment:
Tested also on Apache 2.4.2 + php_module (from www.apachelounge.com) + PHP 5.4.0 VC9 Thread Safe
Test script still crashes.
Previous Comments:
------------------------------------------------------------------------
[2012-04-16 16:37:16] bugzilla33 at gmail dot com
When use #^(A{1}B)+$# instead of #^(A{1,2}B)+$#
testcase returns 1 - no crash
------------------------------------------------------------------------
[2012-04-16 16:34:13] bugzilla33 at gmail dot com
...and I tested Windows 7 only (32-bit and 64-bit)
------------------------------------------------------------------------
[2012-04-16 16:31:13] bugzilla33 at gmail dot com
...but using apache module phpinfo also says:
pcre.backtrack_limit 1000000
pcre.recursion_limit 100000
------------------------------------------------------------------------
[2012-04-16 16:29:34] bugzilla33 at gmail dot com
str_repeat('AB',200) do not crash
str_repeat('AB',300) crashes - browser freeze about 4sec and info - browser can not
display site
------------------------------------------------------------------------
[2012-04-16 16:18:15] rasmus@php.net
Windows-only, I assume? Apache uses PCRE as well, so perhaps Apache on Windows is
resetting the PCRE limits? I assume it doesn't crash if you reduce the 300 there
to something smaller?
------------------------------------------------------------------------
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=61744
--
Edit this bug report at https://bugs.php.net/bug.php?id=61744&edit=1