Silverstripe Version:
Reproduced in 4.3 to 4.5-rc1
Question:
On a new Silverstripe install (with Imagick enabled) adding a handful of large images to a standard page, then running ?flush=1
seems to bypass the 256MB PHP memory limit and (on this particular server) ends up hitting the 1GB LVE memory limit (CloudLinux), causing the request to fail with a 503 error.
Is this expected behaviour?
-
Running
?flush=1
on a different page, with no images, works fine. -
It had no issues generating the smaller versions of those images when they were added and the page viewed normally.
-
Adding the new
?execmetric=1
variable to the URL in my local dev version shows it as only reaching 30MB memory for the same request. -
Adding
Environment::setMemoryLimitMax('200M')
toconfig.php
doesn’t seem to make a difference. -
Example page with issue: http://ss450.pswd.biz/image-test/