Home›Support›English Support›[Resolved] fatal error due to Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)
[Resolved] fatal error due to Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing a fatal error reported by "Fatal Error Notify" due to memory exhaustion when switching the website language from French to English on the page /wheelchair-lifts/. The error message indicates that the allowed memory size is exhausted. Clearing the cache temporarily fixes the issue. Solution: We recommend disabling the "Fatal Error Notify" plugin and then monitoring the site for errors by checking the
/wp-content/debug.log
file. If the error persists, it might not be related to WPML but could be a false notification from the "Fatal Error Notify" plugin. If the error does not appear in the debug log and cannot be replicated on the staging site with the plugin disabled, the issue might be with the plugin itself sending false notifications.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Disabled "Fatal error notify" on staging. I just disabled the object cache on production because I don't want people to see a fatal error. Two colleagues reported the fatal error earlier. We definitely have that, Andreas. Sorry, I can't provide more information. Thanks.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I deleted the debug.log on the staging site, went to
hidden link
and hidden link
and
hidden link
and hidden link
The reported error was not displayed on any of these pages and is not part of the debug.log.
There are only Deprecated Notices showing up which should not impact the site in its current state.
If you replicate the issue on the staging site without "Fatal Error Notify" then we can take further steps.
If you can not replicate the error, then this is a topic for the support of "Fatal Error Notify", as this plugin seems to send you false notifications.
Andreas, the plugin doesn't matter to me. I'm seeing a fatal error after a long loading time. I just installed the plugin to catch the issue and then clear the cache. That's okay though I disabled the object caching and the problem was resolved.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I am sorry to repeat myself, but I could not catch the mentioned error on the staging site.
Please test on the staging site if you can recreate the error while "Fatal Error Notify" is disabled, as this seems to be a false positive send by this plugin.