Bug #81167 [Com]: Segfault when loading a large file

From: Date: Fri, 18 Jun 2021 12:58:14 +0000
Subject: Bug #81167 [Com]: Segfault when loading a large file
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-234486@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=81167&edit=1 ID: 81167 Comment by: kochnorman at rocketmail dot co Reported by: kochnorman at rocketmail dot com Summary: Segfault when loading a large file Status: Open Type: Bug Package: Scripting Engine problem Operating System: Debian 10 PHP Version: 7.3.19-1~deb10u1 Block user comment: N Private report: N New Comment: I cannot easily update, though I will try and will post when I'm done. I've disabled xdebug and it doesn't appear in the list anymore. But the segfault still persists. The bt is: Core was generated by `php -l test.php'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000556d88639bb7 in destroy_op_array () (gdb) bt #0 0x0000556d88639bb7 in destroy_op_array () #1 0x0000556d8865410d in zend_hash_destroy () #2 0x0000556d8864498d in ?? () #3 0x0000556d885e52aa in php_module_shutdown () #4 0x0000556d884aab77 in ?? () #5 0x00007fdad0e7809b in __libc_start_main (main=0x556d884aa6d0, argc=3, argv=0x7fff647f6918, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff647f6908) at ../csu/libc-start.c:308 #6 0x0000556d884aac7a in _start () Previous Comments: ------------------------------------------------------------------------ [2021-06-18 12:39:05] nikic@php.net > I've created a core dump which is available under > https://optimalbliss.de/core-php.329.zip . Sorry for not upload them > here, but I found no way of doing that. Would it be possible for you to extract the backtrace from the core dump? Something like "gdb path/to/php path/to/core" and then "bt" should do it. Analyzing a core dump requires the original binary to be available, so it's hard to do this on a different machine. It may be worth trying whether it works without xdebug. That's the only extension that looks problematic. ------------------------------------------------------------------------ [2021-06-18 12:34:44] cmb@php.net PHP-7.3 is no longer actively supported[1]. Can you please try with latest PHP 7.4 or 8.0? [1] <https://www.php.net/supported-versions.php> ------------------------------------------------------------------------ [2021-06-18 09:53:17] kochnorman at rocketmail dot com I've created a core dump which is available under https://optimalbliss.de/core-php.329.zip . Sorry for not upload them here, but I found no way of doing that. My php -m gives me: [PHP Modules] calendar Core ctype date dom exif fileinfo filter ftp gd gettext hash http iconv imagick json libxml memprof mysqli mysqlnd openssl pcntl pcre PDO pdo_mysql Phar posix propro raphf readline Reflection session shmop SimpleXML sockets sodium SPL standard sysvmsg sysvsem sysvshm tokenizer wddx xdebug xml xmlreader xmlwriter xsl Zend OPcache zip zlib [Zend Modules] Xdebug Zend OPcache I hope this helps researching this bug. ------------------------------------------------------------------------ [2021-06-18 09:31:25] krakjoe@php.net 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. I also cannot reproduce. A copy of the trace is necessary most likely, and also a list of extensions. ------------------------------------------------------------------------ [2021-06-18 09:25:03] nikic@php.net I can't reproduce this on any supported PHP version. I also tried this with more functions (50000 instead of 1000) with same result. ------------------------------------------------------------------------ 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=81167 -- Edit this bug report at https://bugs.php.net/bug.php?id=81167&edit=1

« previous php.bugs (#234486) next »