Segmentation fault (11)

  • Resolved tokkonopapa

    (@tokkonopapa)


    8 years, 2 months ago

    Hi,

    While I scanned wordpress, I got the following error in apache_error.log under the PHP 5.6.10 and WordPress 4.7:

    child pid 1408 exit signal Segmentation fault (11)

    WP_Core and Themes at Quick Scan were OK, but Plugins ended in the same result. I though it was caused by memory error. So I put the followings into wp-config.php but did not resolve this issue.

    define('WP_MEMORY_LIMIT', '1024M');
define('WP_MAX_MEMORY_LIMIT', '1024M');
set_time_limit( 0 );

    I installed 31 plugins and 29 activated. Is it too much plugins?
    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Eli

    (@scheeeli)

    Here is a good article about “HOW TO FIGURE OUT WHAT IS CAUSING AN APACHE SEGMENTATION FAULT”:
    https://sysadmin.carlusgg.com/?p=197

    If this is not your server or it is shared hosting then you would need the server admin to look into it. You may not have permissions to alter the memory_limit in your code.

    Thread Starter tokkonopapa

    (@tokkonopapa)

    Hi Eli,

    Thank you for the information. But unfortunately I can’t re-compile PHP or apache. If I assume this issue might be caused by memory limit, how much does it need? 2GBytes? I can configure memory_limit on my server.

    When I set “Scan Depth” as 3, then “Run Complete Scan” would finish but there were several segmentation fault, and found 3 Read/Write Errors. One was related to .../wordpress/wp-content/plugins/gotmls/index.php which couldn’t finish “Scan Details”.

    So I hope you to improve the process of scanning integrity of file because the line of code is not so many.

    Anyway, thanks for your response.

    P.S. This issue is not resolved but I close it.

    • This reply was modified 8 years, 2 months ago by tokkonopapa.
    Plugin Author Eli

    (@scheeeli)

    I don’t think this is a memory_limit issue and I wouldn’t suggest increasing it any more. I think you current memory_limit setting of 1GB is way too high and I think 2GB would be a really bad idea. I don’t know how much memory your server has but you don’t want every PHP process to be able to use up a Gig of memory. I have used my plugin on lots of servers with the memory_limit set to only 128MB – 256BM and it works fine. The Complete scan is specifically designed to work with minimal memory_limit settings. I think there are other problems on your server if you are getting Read/Write Errors and Segmentation faults.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Segmentation fault (11)’ is closed to new replies.