Memory Allocation error

  • Resolved Tuscanytrace

    (@tuscanytrace)


    8 years, 6 months ago

    I want to alert you that this current version triggers a fatal error when combined with Caldera Forms. Sometimes it just says “memory allocation error” and indicates one of Caldera Forms’ files, and sometimes Sucuri’s. But the worst thing it does is disable the plugin page with this error. It does this whether or not caching is cleared or not, so it’s creating a loop or something. Renaming either plugin file makes it go away, and I can rename either plugin to get it working again, although without the other plugin working.

    Not sure why it’s doing this, but I thought you’d want to know of this new conflict. A lot of people use both as top in their categories.

Viewing 4 replies - 1 through 4 (of 4 total)
  • yorman

    (@yorman)

    8 years, 6 months ago

    Thanks for the report, I will check the compatibility between these two plugins.

    […] But the worst thing it does is disable the plugin page with this error.

    This is a WordPress thing, it automatically disables any plugin or theme that fails to load during the execution of the “init” hook. This is a fail-safe way to keep running your website without being affected by whatever the plugins are failing for.

    Can you please share which page of the Sucuri plugin is triggering the memory allocation error? This only happens when a piece of code is assigning too much data into a variable that the server can handle. I an address this issue today if you can tell me which page is triggering this message.

    Thread Starter Tuscanytrace

    (@tuscanytrace)

    8 years, 6 months ago

    It is dealing with the plugin page in the back end. Attempting to load it or click on anything if it’s already loaded triggers this. Coming into it from Plugins or Add New does the same thing.

    And I do remember the days when something like this would result in the website being disabled, back in 2005 or even 2008. I’m thankful it is now a really rare happening, instead just failing to execute and returning error messages.

    Thread Starter Tuscanytrace

    (@tuscanytrace)

    8 years, 6 months ago

    Also, I meant it disables the *entire* plugin page for all plugins–the core WordPress pages All Plugins, Add New Plugin, etc. It is necessary to go in through the server to disable either Caldera or Sucuri in order to access that page again. If I can trigger it again, I will.

    yorman

    (@yorman)

    8 years, 5 months ago

    Hello @tuscanytrace were you able to find the trigger for the memory allocation issue between the Sucuri plugin and Caldera Forms?

    I have tried to reproduce this problem in multiple servers and it never happens. I wonder if there is something else in your website that is contributing to the exhaustion of the memory and so coincidentally something in one of these two plugins is just adding the last drop of water into the almost full glass, which would explain why it happens inconsistently.

    I will mark this ticket as resolved as this may just be an edge case, it doesn’t seems to be affecting any one else. Feel free to re-open the ticket if you have more information to share so I can continue the investigation. I also suggest you to report the problem to the developers of Caldera Forms so they can also take a look.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Memory Allocation error’ is closed to new replies.