#3273 - PHP ERROR [1] Out of memory - Comments

This is a spacer post for a website comment topic. The content this topic relates to: #3273 - PHP ERROR [1] Out of memory

Is this a persistent problem, or a one-off?

It's on the Admin Zone dashboard?

If this is currently an issue on your site I'll need access to take a look. Currently I can't reproduce. I tried adding 200 test entries of every content type, but am under 20MB of memory use.

Persistent in the admin zone only after changing some benign settings. I assumed you could backdoor in, what info do you need from me?

(Click to enlarge)

Ah, it's probably an issue with a flushed cache. We do see this sometimes on some servers.
I'll try and be scientific about it, I'll do a memory analysis of each template's compilation and see if I can find any thing obvious to optimise.

Out of interest, I wonder if your PHP build is 64 bit.

Just switched to PHP Version 7.0.17
Linux web172.extendcp.co.uk 2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Apr 11 17:13:24 UTC 2017 x86_64

Not sure if it's x64 or not from that, but I get a blank admin screen with php7 so switched back to 5.6.

(Click to enlarge)

I couldn't find an issue on my machine or any obvious bottlenecks, but PHP may use wildly different performance characteristics on different machines I find.

I have made a nice optimisation. The first time CSS and JS is compiled, it will happen in separate requests, rather than the main request. Not only will that reduce memory consumption of the main request, it will also parallelise compilation, which is a great thing.

These files on github:
data/script.php (new)
sources/ajax.php
sources/web_resources.php
themes/default/templates/JAVASCRIPT_NEED_FULL.tpl (new)

Well my other site on the same domain, the main site at surfrenzy.net is fine, so I am sure something I did in config caused the issue with kal.surfrenzy.net which I haven't rectified yet. Will try these new files.

If you still have an issue, I'd need FTP access (or similar) to run tests.
[email protected]

I will send the info, I left it in case you wanted to take a look in the hopes it might lead to this issue not happening again.

Okay, I have updated the files listed above and the issue still persists. Manually cleared caches. I did fix the css issue on the frontend which I mentioned in my most recent email, that was my mistake. I am happy to just reinstall and start fresh but I won't be doing that today, so if you want to take a look feel free if you find some time.

I'll take a look

Did you intentionally disable the template cache?

I am wondering if it is blanking out options, or if you disabled that intentionally.

I planned to do stuff with catalogue templates, so yes I recall I turned all the caches off, not just the template one.

Ah ok. I think that's the issue, it's not using too much memory if there's no caching there. I'll see what I can do.

I wouldn't advise turning that cache off though, Composr is pretty good about auto-decaching edited templates. It's the block cache which tends to be the most problematic one.

Ahh alright, I just figured when I working on stuff it made sense to turn caching off until I'd done, and then I got the memory error. I changed a few settings though, not just the caches,

Should work now :)