Edit report at https://bugs.php.net/bug.php?id=73183&edit=1
ID: 73183
Comment by: schnederle at futureweb dot at
Reported by: schnederle at futureweb dot at
Summary: Segfaults / zend_mm_heap corrupted
Status: Open
Type: Bug
Package: Reproducible crash
Operating System: Centos 7.2.1511
PHP Version: 7.0.11
Block user comment: N
Private report: N
New Comment:
Since I increased opcache.interned_strings_buffer from 8 to 16 there was no single SEGFAULT anymore
... guess the Problem must lie somewhere within Interned Strings Buffer Logic then?
Previous Comments:
------------------------------------------------------------------------
[2016-12-01 16:23:13] schnederle at futureweb dot at
Some new Information - Today I set OPCache Log Level to Debug ... no Segfault so far - but some
other weird Errors - maybe somehow related to the Segfaults Problem?
At first some of those:
< Thu Dec 1 11:44:34 2016 (12618): Warning Interned string buffer overflow
< Thu Dec 1 11:44:34 2016 (12618): Warning Interned string buffer overflow
< ...
< ...
< ...
< Thu Dec 1 11:44:34 2016 (12618): Warning Interned string buffer overflow
< Thu Dec 1 11:44:34 2016 (12618): Warning Interned string buffer overflow
Right after those Errors - some OOM Errors occured:
< [Thu Dec 01 11:45:52.556057 2016] [:error] [pid 11958] [client 80.110.0.0:50912] PHP Fatal
error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 6935160699037703352
bytes) in /var/www/path/html/includes/path1/file.php on line 38, referer: http://www.domain.at/admin/menue/fil...111&id_usr=111
Line 38 of the File where OOM occured:
< if (!function_exists("get_galleries")) {
Did increase opcache.interned_strings_buffer from 8 to 16 now ... but there shouldn't be such
OOM Troubles when reaching Limit I guess ... (not to speak about 'maybe' Segfaults ...)
------------------------------------------------------------------------
[2016-11-23 08:58:52] schnederle at futureweb dot at
still no luck with 7.0.13!
Maybe this additional Information can help?
Followed by the Segfaults I often see those Kind of Errors within Logs:
----------------------------------
error_log-20161116:[Tue Nov 15 14:35:52.478805 2016] [:error] [pid 30926] [client 80.110.0.0:54073]
PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate
140380662153216 bytes) in /var/www/path/html/templates/path/php/news_nuggets.php on line 218,
referer: http://domain
----------------------------------
216 Alle
217 </div>
218 <div class="referenzen_cst_filter_right_entry<?php
if(isset($_GET['filter']) && $_GET['filter'] == 2) { ?>
active<?php } ?>" id="referenzen_entry_2" rel="2">
219 Tourismus
220 </div>
----------------------------------
As one can see - there is nothing which could take 127TB of Memory on Line 218 ... could it be that
OpCache is trying to Output complete nonsense?
------------------------------------------------------------------------
[2016-10-28 08:30:03] schnederle at futureweb dot at
Unfortunately no News yet ... same Problems occur with 7.0.12
Still hoping for some News on this Topic from PHP Guys! ;-)
------------------------------------------------------------------------
[2016-10-20 12:43:10] cadonline at gmx dot net
We are facing similar Problems on our Servers - Did you already find a Solution Andreas?
thx
Markus
------------------------------------------------------------------------
[2016-10-04 10:54:25] schnederle at futureweb dot at
Don't know if it helps ... some more Segfault BTs:
02.10.2016: http://temp.in.futureweb.at/php/core.25917.bt.txt
03.10.2016: http://temp.in.futureweb.at/php/core.20048.bt.txt
04.10.2016: http://temp.in.futureweb.at/php/core.27118.bt.txt
------------------------------------------------------------------------
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=73183
--
Edit this bug report at https://bugs.php.net/bug.php?id=73183&edit=1