Find themes/plugins results in a segmentation fault. #5184
-
|
Whenever I click on Find Themes or Find Plugins, I get an error. Something this drastic leads me to believe I have missed an installation step, or some other "non-bug" explanation. Anybody have an idea of where to start digging? My google-fu is lacking on this one. In chrome, it appears as ERR_NO_RESPONSE, but if I check the Apache error log, I see a child process has seg-faulted at the timestamps I make the requests. I'm running a dedicated Debian 11 server with just a LAMP stack. Info dump: ============================================= Security level Site Theme Admin Theme Install date Server PHP Version MySQL Charset |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
e107 was previously affected by a segmentation fault bug in PHP 8.2.0 (php/php-src#10200), but we applied a workaround in 6b75f34 that is in e107 v2.3.3. PHP 8.2.0 is not an official version included with Debian 11 (Debian 11 had PHP 7.4.21 while Debian 12 had PHP 8.2.5). Can you upgrade it to PHP 8.2.15 and see if the segmentation fault still happens? If not, can you compile PHP with the You can also hook up Xdebug and step through every line of code until you encounter the one that crashes PHP. Yet another way is to obtain a core dump from the segmentation fault and generate a backtrace from that core dump. |
Beta Was this translation helpful? Give feedback.
-
|
8.2.15 did the trick for both plugins and themes. Thanks! |
Beta Was this translation helpful? Give feedback.
e107 was previously affected by a segmentation fault bug in PHP 8.2.0 (php/php-src#10200), but we applied a workaround in 6b75f34 that is in e107 v2.3.3.
PHP 8.2.0 is not an official version included with Debian 11 (Debian 11 had PHP 7.4.21 while Debian 12 had PHP 8.2.5). Can you upgrade it to PHP 8.2.15 and see if the segmentation fault still happens?
If not, can you compile PHP with the
--enable-debugoption to see if you get any assertion failures?You can also hook up Xdebug and step through every line of code until you encounter the one that crashes PHP.
Yet another way is to obtain a core dump from the segmentation fault and generate a backtrace from that core dump.