Bug #73183 [Asn->Csd]: Segfaults / zend_mm_heap corrupted

From: Date: Wed, 09 Jun 2021 15:00:30 +0000
Subject: Bug #73183 [Asn->Csd]: Segfaults / zend_mm_heap corrupted
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-234306@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=73183&edit=1

 ID:                 73183
 Updated by:         cmb@php.net
 Reported by:        schnederle at futureweb dot at
 Summary:            Segfaults / zend_mm_heap corrupted
-Status:             Assigned
+Status:             Closed
 Type:               Bug
 Package:            Reproducible crash
 Operating System:   Centos 7.2.1511
 PHP Version:        7.0.11
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

The point is that prior to PHP 7.2.0, there have been known issues
regarding interned strings.  I assume that this issue has been
fixed, so I'm closing.  If you happen to reproduce it with any
actively supported PHP version, feel free to reopen or file a new
ticket.


Previous Comments:
------------------------------------------------------------------------
[2021-06-09 14:57:02] schnederle at futureweb dot at

@cmb - unfortunately I cannot test it on the affected system. The system is live & productive, I
can't do a deliberately induced downtime here. Since the segfaults occurred sporadically and
unfortunately I could not find a testcase with which I can trigger the segfault, unfortunately I
currently have no way to test it.
The affected CMS is currently running on PHP 7.2.34, but with the option
"opcache.interned_strings_buffer = 16" which also fixed the problem with V7.0.x ...
best regards
A.

------------------------------------------------------------------------
[2021-06-09 14:47:22] cmb@php.net

Is this still an issue with any of the actively supported PHP
versions[1]?

[1] <https://www.php.net/supported-versions.php>

------------------------------------------------------------------------
[2018-06-28 15:23:49] t dot motylewski at gmail dot com

and a few more:
https://bugs.php.net/bug.php?id=69251
https://bugs.php.net/bug.php?id=59191

------------------------------------------------------------------------
[2018-06-28 15:06:26] t dot motylewski at gmail dot com

similar issues:
https://bugs.php.net/bug.php?id=73598
https://bugs.php.net/bug.php?id=65590
https://bugs.php.net/bug.php?id=66569

------------------------------------------------------------------------
[2016-12-19 12:01:23] schnederle at futureweb dot at

I can confirm that raising opcache.interned_strings_buffer from 8 to 16 MB did solve that Segfault
issues! ~3 Weeks without a single Segfault ...

Actual OPCache Stats - interned_strings_usage - more than the initial 8MB are used ...

----------------------------------------------------
Array
(
    [opcache_enabled] => 1
    [file_cache] => /var/www/ortsinfo/opcache
    [cache_full] => 
    [restart_pending] => 
    [restart_in_progress] => 
    [memory_usage] => Array
        (
            [used_memory] => 86297760
            [free_memory] => 47915104
            [wasted_memory] => 4864
            [current_wasted_percentage] => 0.0036239624023438
        )

    [interned_strings_usage] => Array
        (
            [buffer_size] => 16777216
            [used_memory] => 8840536
            [free_memory] => 7936680
            [number_of_strings] => 74538
        )

    [opcache_statistics] => Array
        (
            [num_cached_scripts] => 4397
            [num_cached_keys] => 12811
            [max_cached_keys] => 16229
            [hits] => 15118014
            [start_time] => 1482122407
            [last_restart_time] => 0
            [oom_restarts] => 0
            [hash_restarts] => 0
            [manual_restarts] => 0
            [misses] => 7
            [blacklist_misses] => 0
            [blacklist_miss_ratio] => 0
            [opcache_hit_rate] => 99.999953697643
        )

)
----------------------------------------------------

Andreas Schnederle-Wagner

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


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


Thread (23 messages)

« previous php.bugs (#234306) next »