I have a category with more than 200 articles in 3 subcategories. when I create a category blogmenu item the view works only with 200 articles loaded, if I select more, I run into a fatal error: allowed memory size exausted error. memory_size_limit is 256M and I cannot increase it with my hosting.
however, if deactivate the jce media-field, the page works! is there something in the plugin, that runs into a loop?
however, if deactivate the jce media-field, the page works! is there something in the plugin, that runs into a loop?
fatal error: allowed memory size exausted error
What file is triggering this error? The error statement should show the file path.
Just because you're not paranoid doesn't mean everybody isn't out to get you.
I see these errors:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 835584 bytes) in /kunden/xxx/webseiten/xxx/neu2023/plugins/system/n3tcookieconsent/n3tcookieconsent.php on line 1229
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 843776 bytes) in /kunden/xxx/webseiten/xxx/neu2023/libraries/vendor/symfony/error-handler/ErrorRenderer/HtmlErrorRenderer.php on line 273
if I deactivate n3tcookieconsent I get this:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 827392 bytes) in /kunden/xxx/webseiten/xxx/neu2023/libraries/vendor/laminas/laminas-diactoros/src/Stream.php on line 246
But all works if I deactivate the jce media field
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 835584 bytes) in /kunden/xxx/webseiten/xxx/neu2023/plugins/system/n3tcookieconsent/n3tcookieconsent.php on line 1229
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 843776 bytes) in /kunden/xxx/webseiten/xxx/neu2023/libraries/vendor/symfony/error-handler/ErrorRenderer/HtmlErrorRenderer.php on line 273
if I deactivate n3tcookieconsent I get this:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 827392 bytes) in /kunden/xxx/webseiten/xxx/neu2023/libraries/vendor/laminas/laminas-diactoros/src/Stream.php on line 246
But all works if I deactivate the jce media field
Does this happen when creating an article or when viewing the article in the front-end?
Just because you're not paranoid doesn't mean everybody isn't out to get you.
Please send me a login - https://www.joomlacontenteditor.net/contact/site-login
Just because you're not paranoid doesn't mean everybody isn't out to get you.
I don't know what is causing this issue.
If I remove all methods from the JCE MediaField plugin , so that it is just a blank class, eg:
the timeout still occurs.
I don't see how the JCE MediaField plugin could be the cause of this.
If I remove all methods from the JCE MediaField plugin , so that it is just a blank class, eg:
class PlgFieldsMediaJce extends FieldsPlugin
{
}
the timeout still occurs.
I don't see how the JCE MediaField plugin could be the cause of this.
Just because you're not paranoid doesn't mean everybody isn't out to get you.
well, I also posted in the Joomla Mattermost channel about it and Richard Fath mentioned the XML-manifest file or manifest_cache table as potential causes or that something is missing from the php code that the core needs (which is also missing with the empty class). but I cannot tell if that's helpful
How many JCE Media Fields are on the page?
Just because you're not paranoid doesn't mean everybody isn't out to get you.
It is used only in articles of one of the three categories, there are 44 articles in this category. the articles in the other categories almost never use the jce media field. I think around 50 - 60 articles in total use it.
I think around 50 - 60 articles in total use it.
I don't think this is any kind of recursion problem, but a capacity issue. There is nothing in the JCE MediaField code that should consume a lot of memory, and no recursion issues either. I think you just ahve a lot of articles with media fields being processed, on top of all the other processing done by other plugins.
I've not been able to find any reasonable change to the code that imprvoes this in this specific instance.
Just because you're not paranoid doesn't mean everybody isn't out to get you.
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!