Title: Allowed Memory Limit Exhausted
Last modified: May 3, 2017

---

# Allowed Memory Limit Exhausted

 *  Resolved [pframe](https://wordpress.org/support/users/pframe/)
 * (@pframe)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/allowed-memory-limit-exhausted/)
 * Noticed yesterday that we are unable to do an “all content export” using the 
   wordpress export.
    Watched the error log and we get 2 errors back to back every
   time we try and run it:
 *     ```
       PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 55878648 bytes) in ******/wp-content/plugins/ssl-insecure-content-fixer/includes/class.SSLInsecureContentFixer.php on line 261, referer: https://******/wp-admin/export.php
       PHP Fatal error:  Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0, referer: https://*********/wp-admin/export.php
       ```
   
 * It makes it look like ssl insecure content fixer is trying to do something very
   memory expensive during the export. We have ours set to content (although changing
   to “all content” didn’t help).
 * Any idea why the fixer is running over anything besides the “export complete”
   text?
    Is it trying to filter the output file somehow? If so why?

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

 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/allowed-memory-limit-exhausted/#post-9095753)
 * G’day [@pframe](https://wordpress.org/support/users/pframe/),
 * Thanks for the bug report! I couldn’t replicate it on my multisite dev environment,
   had to go to a single site to see it. I’ve fixed it for the next release, and
   you can get a preview of it here if you like:
 * [https://www.dropbox.com/s/8ban14o77q5a9nv/ssl-insecure-content-fixer-2.3.1-dev.zip?dl=1](https://www.dropbox.com/s/8ban14o77q5a9nv/ssl-insecure-content-fixer-2.3.1-dev.zip?dl=1)
 * cheers,
    Ross
 *  Thread Starter [pframe](https://wordpress.org/support/users/pframe/)
 * (@pframe)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/allowed-memory-limit-exhausted/#post-9098139)
 * Oh I should have mentioned that it was a non-network install that was having 
   the issue.
    The updated plugin worked perfectly thank you!
 *  Plugin Author [webaware](https://wordpress.org/support/users/webaware/)
 * (@webaware)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/allowed-memory-limit-exhausted/#post-9098867)
 * No worries! I’ll have to go hunting for other admin things that I’m breaking 
   now 🙂
 * cheers,
    Ross

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

The topic ‘Allowed Memory Limit Exhausted’ is closed to new replies.

 * ![](https://ps.w.org/ssl-insecure-content-fixer/assets/icon-256x256.png?rev=2590634)
 * [SSL Insecure Content Fixer](https://wordpress.org/plugins/ssl-insecure-content-fixer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ssl-insecure-content-fixer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/)
 * [Active Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [webaware](https://wordpress.org/support/users/webaware/)
 * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/allowed-memory-limit-exhausted/#post-9098867)
 * Status: resolved