hallowelt55

Currently a free user.
I’ld like to share my url but not publicly. Is there a way to contact you directly via PM?

No, the problem has not been resolved.

I checked with my hosting provider and php memory limit for my site is already set to a max of over 700MB. So the problem has to be related to the plugin.

If you read my last message in detail, you see that error message says it tried to allocate 9223372036854775840 bytes, that’s like 9223372036 GB. Doesn’t that look suspicious to you in any way?

I also figured out, the underlying link for the download looks something like this: …/download/filename/?wpdmdl=14854&refresh=600e7752606f81611560786

The download of the file works when I remove the ‘refresh’ argument. Still shows the error but at least starts the download. I think it has to be some issue with the stats tracking.

I should also mention, that everything works totally fine when I am logged into my WordPress backend. Only causes these warnings and errors when accessing from the outside like a normal visitor.

Btw, thanks for taking the time to responding to my questions. I know you only try to help, I just need to figure out the root of the issue.

• This reply was modified 3 years, 10 months ago by hallowelt55.
• This reply was modified 3 years, 10 months ago by hallowelt55.
• This reply was modified 3 years, 10 months ago by hallowelt55.
• This reply was modified 3 years, 10 months ago by hallowelt55.
• This reply was modified 3 years, 10 months ago by hallowelt55.

Again I am running into these kinds of errors. I am just wondering, why does the plugin try to allocate these enormous file sizes?

Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 9223372036854775840 bytes) in …public_html/wp-content/plugins/download-manager/libs/class.DownloadStats.php on line 50

Please explain it to me. I want to understand it.

Hi,

thanks for the quick response and your suggestions.
However, I am wondering if increasing the memory limit is really necessary and a sustainable solution. Can you explain to me what this huge usage of memory is caused by? I mean what action in the whole process of downloading a file (not bigger than 2MB) and updating the stats could use that amount of memory? Just curious.

Thanks in advance

Ok. I have an update. Seems like I got it fixed temporarily.
After deactivating the “Combine CSS” option, all combined CSS files were deleted from the /wp-content/uploads/siteground-optimizer-assets path. Now after reactivating, at first only one new combined CSS filed was added to that folder, after a waiting for some time now 9 different combined CSS files are available in this folder. And all pages now seem to refer to one of the currently existing combined css files and the pages are not broken anymore.

But I still don’t understand how these mechanics of generating and deleting combined css files work. How can I prevent this from happening?
To me it seems the root cause is that somehow these combined CSS files were deleted on the server without re-generating and linking a new one. Thus, the respective pages where still trying to fetch their CSS file under the old path.

Any advice here?