Fatal error: Allowed memory size

That’s way too much memory. Maybe there is a bug in reading the mo files (that’s when streams.php gets involved). Does this error happen while activating or after activation? And which plugins are installed?

The error occurs when activating the plugin.

The installed plugins are:
– Add from Server
– Admin Menu Editor
– Advanced Page Manager
– Akismet
– All in One SEO Pack
– BAW Post View Count
– Broken Link Checker
– Google Analycator
– Google Publisher Plugin
– Google XML sitemaps
– Plugin Organizer
– Real Simple Captcha
– Related Post Thumbnails
– Revelanssi
– WP-Optimize
– Better WordPress Recent Comments
– Meta Slider
– Contact Form 7
– MailPoet Newsletters
– Comprehensive Google Map Plugin
– Facebook
– Shareolic
– JS & CSS Script Optimizer
All are up-to-date.

Ok, I’ll try to reproduce the error. I guess it’s a problem with one of the language files. Maybe it’s a bug in the mo reader, maybe an error in one of the files.

One more thing: Could you post the full stack trace from the error (maybe you have to activate debugging so it gets displayed). That way maybe I can determine faster where exactly the error occurs.

I could identify the problem: It is caused by the French language file of All In One SEO Pack. It seems to me, the file is corrupted. The default WordPress implementation doesn’t load the translations (All In One SEO stays in english). WPPP doesn’t catch the error and tries to read insanely large strings (caused by erroneous tables in the mo file – the first few entries seem fine, then suddenly offsets and sizes get out of control, so to say).

Quick fix: Delete all_in_one_seo_pack-fr_FR.mo from all-in-one-seo-pack directory.

I’m going to implement some sanity checks so WPPP will catch such corruptions instead of trying to allocate that insane amount of memory.

Version 1.7.4 fixes this issue as it performs some simple integrity checks on mo file contents. This causes the french translation of All In One SEO Pack not to be loaded (as does wordpress’ default implementation).

Thanks for you very fast correction. I confirm that this solves the issue on my website.