3.1.13 seems to cause PHP timeout

  • Resolved dccs52

    (@dccs52)


    3 years, 9 months ago

    Great plugin! Thank you for the hard work, it does not go un-noticed.

    It seems having upgraded to 3.1.13 from 3.1.08 the download pages that seem to have a lot of downloads (400+) in a JS table seem to timeout and not show any downloads.

    I found the only way to solve this is to clear the history table, it seems as soon as that starts to fill up for a few days (on a busy site) the downloads list will need not load and we get “There has been a critical error on this website” to which if we check the debug log it comes down to

    [02-Feb-2021 11:30:45 UTC] PHP Warning: Illegal string offset ‘601937e58b9a0’ in /home/#/public_html/#/plugins/download-manager/libs/class.DownloadStats.php on line 50
    [02-Feb-2021 11:30:45 UTC] PHP Fatal error: Allowed memory size of 1258291200 bytes exhausted (tried to allocate 9223372036854775840 bytes) in /home/#/public_html/#/plugins/download-manager/libs/class.DownloadStats.php on line 50
    [02-Feb-2021 11:30:47 UTC] PHP Warning: Illegal string offset ‘601937e7c120f’ in /home/#/public_html/#/plugins/download-manager/libs/class.DownloadStats.php on line 50
    [02-Feb-2021 11:30:47 UTC] PHP Fatal error: Allowed memory size of 1258291200 bytes exhausted (tried to allocate 6019370000032 bytes) in /home/#/public_html/#/plugins/download-manager/libs/class.DownloadStats.php on line 50
    [02-Feb-2021 11:31:35 UTC] PHP Fatal error: Out of memory (allocated 492756992) (tried to allocate 60149024 bytes) in /home/#/public_html/wp-includes/wp-db.php on line 2056

    I have downgraded to 3.1.11, just in case this can fix the issue until it is resolved.

    I should add the site is on a dedicated VPS, has loads of mem etc… and never had this issue

    UPDATE
    I found the latest version is actually creating nearly 900mb of overhead in the postmeta database, having cleared that and rolled back to 3.1.08 seems to solve the issue for all the above

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Nayeem Hyder

    (@nriddhi)

    Has the problem been resolved? please let me know

    thanks

    Thread Starter dccs52

    (@dccs52)

    No sorry, the issue still exists if i upgrade to 3.1.11, currently using at 3.1.08 and the issue does not appear. It seems the latest update causes the database to bloat hugely with a massive overhead being created by the above query. If i enable the latest version after only a few downloads, the overhead starts building up to around 5-7mb! Using 3.1.08 the overhead maintains a steady increase in KB and is completely normal/and expected. Something has changed between versions which creates a massive bloat on the DB, linked to the stat history it seems. Will need to remain at 3.1.08 until the issue can be found by the plugin author.

    It has been a month since this big problem occurred. It`s not solved in 3.1.14 either. It would be nice to hear something from the devs.. they just tell people to increase the memory size limit to 1024 MB. Maybe next year…

    • This reply was modified 3 years, 9 months ago by arakelian.
    • This reply was modified 3 years, 9 months ago by arakelian.

    Any news about this issue? I`m still running an older version. Why is this problem still persisting after a month?

    Thread Starter dccs52

    (@dccs52)

    Has the latest version fixed this issue, the changelog is very vague, it mentions, Improved Query class?

    Can the dev help us here?

    I should add that the work on this plugin is greatly appreciated. Just wanted to add that as i’m aware if the dev reads this, it may appear that we don;t appreciate the work.

    Plugin Contributor Shafaet Alam

    (@shafayat-alam)

    Hi,
    Sorry for the delayed reply and thanks for your patience. Yes, the issue is fixed in the latest version ( 3.1.15 ).

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘3.1.13 seems to cause PHP timeout’ is closed to new replies.

Tags