• Resolved littleantz

    (@littleantz)


    I just updated slimstat minutes ago and after update the site breaks.

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 213998 bytes) in /home/site/public_html/website/wp-content/plugins/wp-slimstat/browscap.php on line 406

    Now my slim stat is dactivated and site working OK.

    Will appreciate immediate fix.

    Anyone else experience this?

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Jason Crouse

    (@coolmann)

    You exceeded your PHP memory limit, it’s something related to your hosting provider, not to my plugin. Try disabling some other hungry plugins and then try again 🙂 My plugin only needs about 3 MB of available RAM on the server to be activated, and less than 1 megabyte to keep going…

    Keep us posted,
    Camu

    Thread Starter littleantz

    (@littleantz)

    Thanks for your reply.

    Like i said, when your plugin is enabled the error persist. I disable yours and things are OK. Enabled and back to that error.

    I disable others, error is persisting when yours is enabled.

    Error goes away only when yours is disabled.

    This happens right after I update to 2.4

    Is there a way to roll back?

    Thanks

    Plugin Contributor Jason Crouse

    (@coolmann)

    Hi there,

    you may want to ask your provider to higher your PHP memory limit, if you want the error to go away. Of course you can roll back to WP SlimStat 2.3, just download it from here, unzip it and upload all the files via FTP to your wp-content/plugins.

    Camu

    Thread Starter littleantz

    (@littleantz)

    site is now OK with 2.3

    Thanks

    Plugin Contributor Jason Crouse

    (@coolmann)

    Cool!

    Thanks,
    Camu

    Plugin Contributor Jason Crouse

    (@coolmann)

    Hi there,

    From tests conducted on my dev environment, my plugin requires about 3 megabytes during activation and less than 1 when executed to track a visit. WordPress itself uses a lot of those 32 mega. Just search google for “WordPress error 32 Meg” and you’ll find a lot of info about this issue. So, long story short, we plugin developers don’t have much left for our stuff. Please take a look at the source code of my plugin before saying it’s poorly implemented 🙂 I’ve tried to use the best practices out there to make my code lighter, more optimized and fast. Unfortunately when you have to deal with geolocalization and info about thousands of browsers, there’s not much you can do to “squeeze” them to take less memory.

    Best,
    camu

    PS: my hosting provider gives me up to 64 mb and it costs me $15/year. Your provider must be really “cheap” 🙂 just kidding…

    Ps2: try to install one of those plugins that tell you how much memory your system is using, you will be able to understand who’s using your ram 🙂

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

The topic ‘2.4 Update breaks the site’ is closed to new replies.