Scan Stops

  • Resolved BruceHalpern

    (@brucehalpern)


    6 years, 9 months ago

    Trying out Media Cleaner for the first time. Start Scan. It stops at Preparing posts (85 posts)…

    php error log shows no errors.

    I ran it first with the Advanced settings at default.

    I tried doing Reset several times.

    I then changed them to try to fix this to Medias Buffer 50, Posts Buffer 1, Analysis Buffer 10, Delay 3000.

    Stops at 86 posts. I assume before it displayed 85 because it was doing 5 at a time. When I switched it to 1 at a time, it stops at 86.

    Scanning has the following checked: Posts, Post Meta, Widgets, Logs.

    Number of posts on website: 237. Media Library contains 8,733 items.

    php version 7.1.4.

    With the Logs box checked, I don’t know where to find the internal log file, as it doesn’t say.

    Thank you in advance for your help.

Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter BruceHalpern

    (@brucehalpern)

    Using version 4.5.7:

    Stuck at Preparing posts (127 posts)…

    [01-Mar-2018 15:49:12 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 18031987 bytes) in /wp-includes/wp-db.php on line 2794

    I can try increasing the allowed memory size. However, what size is going to be enough? Is it just going to keep grabbing more no matter how much I allow or is the size currently set lower than it should be in general?

    In other words, is my allowed memory lower than it should be or is there a memory bug?

    I changed the Advanced settings to be as slow and minimal as possible in order to avoid stressing the server.

    Medias Buffer: 50
    Posts Buffer: 1
    Analysis Buffer: 10
    Delay (in ms): 2000

    Thank you for your help.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi,

    Double it and see what happens ?? There is no memory “bug”, the process uses memory, the bigger your install is. I could enhance this a bit actually but that would slow down the process too. I am constantly juggling between people with “memory issues” and “performance issues”, not easy ?? Your settings are fine.

    Thread Starter BruceHalpern

    (@brucehalpern)

    I changed these to the following in the wp-config.php file:

    define(‘WP_MEMORY_LIMIT’, ‘512M’ );
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

    It then ran until:

    Error at 3940/8851 (45%):

    I told it to Ignore and it then displayed:

    There are 1,332 issue(s) with your files, accounting for 4,674.54 MB. Your trash contains 0.00 MB.

    The error log contains the following:

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 21507724000 bytes) in /wp-content/plugins/media-cleaner/common/admin.php on line 317

    So, it appears that it will work for about 1,000 media entries and then stops with an out of memory issue.

    I’ve told it to delete the 1,332 items it says are not in use.

    So, I can keep running it until it has checked all 8,851 media files we have.

    Thank you for your help.

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi,

    That’s not really about the number of media entries you have, it’s more about the number of references to them you have ?? It seems you might… have a lot. Do you have a very big website with a huge amount of content?

    The plugin creates this cache and currently, it’s one big array. In the future, I plan to make a specific table in the DB to keep track of those. To avoid this issue, basically ??

    I am still fixing tiny issues here and there, I want to make it perfect before jumping to this next big optimization. The issue you are having impact less than 1% of my users which is why I didn’t make it priority, but it is still relatively a big impact so I will need to do it.

    I’m having the same issue.

    Plugin Author Jordy Meow

    (@tigroumeow)

    @ohokic Same issue but maybe different causes, there is an infinity of them ?? Can you try the very latest version? And also, look at your PHP Error Logs.

    Hey @tigroumeow,

    I have the latest version of the plugin. Debug.log shows no recent errors.

    Update, I disabled all plugins and the scan ends here:

    Error at 0/5161 (0%): Request Timeout

    Still nothing in the PHP error log

    Plugin Author Jordy Meow

    (@tigroumeow)

    Please have a look at this page, I have just written it now, and will improve it the best I can: https://meowapps.com/debugging-wordpress/request-timeout/

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘Scan Stops’ is closed to new replies.