Closed appyapp closed 8 years ago
@appyapp I'm sorry about this issue. I've never experienced anything similar ... but once we got a report from some user who suffered this. The good news is that the next stable version of the bundle (to be released very soon) has changed completely the wat we process configuration. This has solved some issues for some people and it may help here too.
As a side comment, it looks like this error is because of the "template cache warmer", which compiles all the Twig templates when you do a cache clear with a warm up. Have you tried to disabled this bundle and see if the error persist? Thanks!
@javiereguiluz When I disable the EasyAdminBundle, I don't hit the memory limit. I tried various test case like: 1 - Loading the bundle without SubCategory Entity : memory limit fatal error 2 - Loading the bundle without SubCategory and Category Entities: memory limit fatal error 3 - Loading the bundle with the defaults entity parameters, i.e :
entity:
- AppBundle\Entity\Race
- AppBundle\Entity\Subcategory
- AppBundle\Entity\Category
Memory Limit Fatal Error 4- Loading the bundle wihout defining entities : Memory Limit Fatal Error So, I uninstalled and reinstalled the bundle, but without changes...
If I remember well, the error had the same origin, the template cache warmer.
I hope the next stable version will improve that small issue. I guess for the moment I have to increase the memory limit. Thanks for your quick response !
Hi Javier,
First of all, thanks to you to provide such an amazing bundle. It's really quite esay to configure and use. But I would like to have your advice on something that disturb me. I created a backend with my three entities :
I did some configuration on the fields shown in list, search,edit,show views. When I try to clear the cache of all my application (in order to override a FOSUser Template for example), I reach the limit of allowed memory for PHP, which is 128MB. I passed it to 256M for the CLI and the cache is cleared without warnings. To resolve memory limit problem, the popular answer is to do what I've done : increase the memory. But for my point of view, it doesn't resolve an unoptimized script... So, is it normal to reach the memory limit with cache:clear in a dev environment and with EasyAdminBundle ? What will happen in the production environment? Will I need 128M or 256M ?
And if you can enlighten where the error comes from, I paste you the output of the command :
And sometimes I get this error:
Thanks in advance,
Pierre