Completely Broke WP Admin

  • Resolved summeralyssa

    (@summeralyssa)


    12 years, 6 months ago

    Sadly, my work WordPress site is hosted by 1and1, which has tight memory allocations. I couldn’t generate NexGen gallery thumbnails, so I decided to figure out which plugins absorbed the most memory in order to do targeted, temporary deactivations. A search revealed P3 as the best tool for the job.

    A quick auto-install and page refresh later, my WP Admin pages vanished completely. The front end was still up and active, but the backend was completely inaccessible. I panicked, then tried a quick and dirty rename of the P3 plugin folder to force deactivation. Everything reappeared.

    Yay for a simple solution, but points deducted for scaring the crap out of me;) I have backups, of course, but still…

    It doesn’t appear to be a common issue, but I thought you should know.

    Browsers used: Chrome and Safari
    Mac OS 10.9

    http://ww.wp.xz.cn/plugins/p3-profiler/

Viewing 1 replies (of 1 total)
  • Plugin Contributor Kurt Payne

    (@kurtpayne)

    12 years, 6 months ago

    Hi summeralyssa,

    Sad to say that this can happen. There’s no way to know how much memory is available (i.e. how high you can turn memory_limit) or will be required to actively profile a site. The debug profiles are generated by php, not by P3, and can be big. PHP has done a good job in recent versions to optimize the memory requirements for debug_backtrace and P3 takes advantage of these optimizations, but again, it’s specific to your php version.

    If you run into this again, you can hit the emergency shutoff switch for P3. Just visit yoursite.com/wordpress/index.php?P3_SHUTOFF=1

    During a scan, P3 will also catch fatal errors automatically turn off scanning. It sounds like you were just right at the tipping point. Sorry your site went down. I’m glad it’s back up now 🙂 I hope you’re able to ferret out the source of your performance problems.

Viewing 1 replies (of 1 total)

The topic ‘Completely Broke WP Admin’ is closed to new replies.