[wp-trac] [WordPress Trac] #44532: Extreme memory leak related to wp_is_stream in wp-includes/functions.php in WordPress 4.9.7

[WordPress Trac]

#44532: Extreme memory leak related to wp_is_stream in wp-includes/functions.php in
WordPress 4.9.7
-----------------------------------------+---------------------
 Reporter:  timbowesohft                 |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  high                         |   Milestone:  4.9.8
Component:  Media                        |     Version:  4.9.7
 Severity:  major                        |  Resolution:
 Keywords:  has-patch reporter-feedback  |     Focuses:
-----------------------------------------+---------------------

Comment (by pbiron):

 Replying to [comment:40 ddenev]:
 > Unfortunately, I got another crash today. Here is the Apache error log:
 >
 > Honestly, I am not sure that this is related since the line in
 functions.php is completely different:
 > {{{#!php
 > $caller[] = "{$call['class']}{$call['type']}{$call['function']}";
 > }}}
 > in `wp_debug_backtrace_summary()` but I'm posting it here as it seems
 again as a memory leak.

 I can't be sure either, but it doesn't appear to me to be related.  Seems
 to have something to do with the `gdpr-framework` plugin.

 And the `memory allocation` error in:

 {{{
 [Sun Jul 15 11:03:27.951018 2018] [php7:notice] [pid 29440:tid 852]
 [client 192.168.88.11:22468] PHP Fatal error:  Allowed memory size of
 268435456 bytes exhausted (tried to allocate 17179869232 bytes) in
 D:\\Projects\\Websites\\bayer-machines\\web\\wp-includes\\functions.php on
 line 5158, referer: https://bayer-machines.ddev/products/plasma-cutting-
 machines/
 }}}

 seems to be the result of QM calling `wp_debug_backtrace_summary()` to
 report on whatever error occurred in `gdpr-framework`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44532#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform