wp-crash after update to 4.4.3

@coastodian

Allowed memory size of 67108864 bytes exhausted

If you look at the error, it is not taking your php setting to increase the memory limit. PHP is currently using about 67 MB as its memory limit. Please ask GoDaddy to help you increase that limit.

Hi Jason,

you’ve prolly figured out by now I am no rocket scientist with respect to wordpress or PHP or web-hosting. I do have a degree in CS from long ago, so neither am I a complete nitwit.

I’ve killed the PHP process on my hosted site and restarted it, cleared caches, quit browsers.

when slimstat is running, I get:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 19922944 bytes) in /home/content/11/7539211/html/wp-content/uploads/wp-slimstat/browscap-db.php on line 65540

when I disable slimstat, the website loads like normal.

Is there any way I can install an old version of slimstat?

I need to spend time doing my non-profit work and writing about it, not troubleshooting my website.

thanks so much for your help.

• This reply was modified 8 years, 1 month ago by coastodian.

Still get a white screen when I update to 4.4.3
Norm

@coastodian, you can download older versions of Slimstat here – https://www.ads-software.com/plugins/wp-slimstat/developers/

@yukoner I’m afraid you too are hitting your PHP memory limit. Can you ask your provider to help?

@coolman Jason, how much memory should I ask for?
Norm (Yukoner)

@yukoner it depends on how many plugins you’re using. From the error log they might be able to see how much more memory WordPress/PHP is trying to allocate and then use that as a starting point.

Hi Jason,

thanks for link to your version archive.

1) can you tell me which was the last version before you made the change with the browscap part that has greater memory demands? (that seems to be what caused things to break for me.

2) How do you recommend I downgrade slimstat so that nothing else breaks?

Thank you for your time.

@coastodian, version 4.4.1 is what you may want to install. DO NOT UNINSTALL the plugin through the WP admin. Just download the zip file, unzip it, and upload its content to your server via FTP (overwrite the existing files).

Jason

@coolman Hi Jason. I asked HostPapa about a PHP increase and they said I’m already at the 128M limit. Guess I’ll stick with 4.4.2 until I figure something else out. Thanks for all the effort you put into this plugin.

@yukoner, do they see any other problems in the webserver error log?

@coolman Jason, the only error log I have access to doesn’t seem to indicate any errors from this issue at all. Far too often the support crews at our ISP resort to cutting and pasting pat answers instead of researching the current issue. In this case they used an outdated direction to locate the error log.

I uninstalled 4.4.2 entirely, including using FTP to remove the directory at /wp-content/uploads/wp-slimstat. Then I installed 4.4.3. Got the white page again, no new error messages.

@yukoner, it might be a permission issue then of some kind. Only the error log can tell.

Plugin was previously working fine but looks like browscap has updated itself today and exceeded memory limit again causing two sites to white screen, so the problem seems to also have potential to arise when browscap updates itself.

After some time getting the sites available again I have turned browscap off and reverted to heuristic method which works fine for me and doesn’t cause these errors and performance issues.

Slimstat is a great plugin, but seems to be getting less and less “slim” with the introdcution of browscap!

@robf thank you for your feedback. We will keep that in mind. Maybe switching to heuristic as the default detection method could solve this issue, even if people might not realize that its accuracy is not as high as the one offered by browscap, and think that Slimstat is just not accurate. In the meanwhile we are performing some tests with the “light” version of Browscap ( https://browscap.org/ ) which is MUCH smaller ( 300KB vs 8MB for the regular data file ). If we determine that it covers most of the common browsers anyway, we might decide to go with it. Again, thank you for your feedback.

Jason

Thanks Jason, that sounds like a good compromise – understood that you’re trying to get the best accuracy, and it might be a bit complicated having a 3 way choice (browscap / browscap lite / heuristic) but that would probably accommodate your wide range of plugin users the best. Much appreciated, Rob