Poprawka: Błąd wyczerpania pamięci WordPress – Zwiększ pamięć PHP

463 komentarzeLeave a Reply

1. Vennh

   sie 2, 2014 at 12:55 pm

   This Worked for me.

   /**This is a test for memory*/
   define(‘WP_MEMORY_LIMIT’, ’64M’);

   Thank you for this wonderful share.

   Odpowiedz

2. joey

   lip 4, 2014 at 2:54 am

   Thanks for the great and simple help! This solved my issue ! Thumbs up;)

   Odpowiedz

3. Lu

   cze 13, 2014 at 7:31 pm

   Should the memory limit ever be higher than 64M? Most WP sites i’ve worked on the average page load never exceeds 40-5megs. The reason I ask, is I read that the WP_MEMORY_LIMIT defines the amount of memory WordPress can use per Apache thread. Which means that multiple threads will use more and more, and eventually swap to disk which is never good.

   Anybody an expert and can answer this?

   Odpowiedz

4. WPBeginner Staff

   maj 26, 2014 at 4:58 pm

   It seems like WordPress is either unable to create wp-config.php file or the file gets deleted after the install. Use ftp to make sure that there is a wp-config.php file present on your site. If not then try creating one by renaming the wp-config-sample.php file to wp-config.php file. You will need to manually edit the file and provide your database information.

   Odpowiedz

5. Billy

   maj 26, 2014 at 7:06 am

   HI how to resove this error

   http://bloggytech.in/wp-admin/install.php

   Please visit this URL…it showing this error, after installing it onceagain its showing the same…..Please reply

   Odpowiedz

6. aiyeboy

   mar 27, 2014 at 5:47 am

   hope i wont be mocked, where do i see the config.php, is it in my phpmyadmin or where pls

   Odpowiedz

   • WPBeginner Support

     mar 27, 2014 at 11:55 am

     wp-config.php file is usually located in the root folder of your website and can be accessed using FTP client or cPanel file manager.

     Odpowiedz

     Admin

     • aiyeboy

       kwi 2, 2014 at 2:06 pm

       if i locate it on an ftp, and i click on it, it brings it like a download file, pls help with a full guide on how to do it pls my site is going down everyday…

       Odpowiedz

       • tony leon

         kwi 4, 2014 at 8:53 pm

         don’t double click it. Either right click and select EDIT or highlight it and look for an EDIT button somewhere (maybe at the top if it’s Godaddy). Good Luck!

7. LJ LaValle

   lut 16, 2014 at 8:47 pm

   I opened the wp-config.php file from my ftp directory.
   I was not sure how to completely enter the adjustment – I didn’t know basic coding for php, so I just copied the basic precursors shown for each entry and added as follows:

   /**This is a test for memory*/
   define(‘WP_MEMORY_LIMIT’, ’64M’);

   It worked!

   Odpowiedz

8. Ali

   sty 31, 2014 at 2:50 pm

   how about i change it to 256 m

   Odpowiedz

9. Doug

   sty 13, 2014 at 10:55 am

   Thank you!!! This fixed a problem I created myself and saved having to pay someone at the hosting company to update the file.

   Odpowiedz

10. kim

    sty 12, 2014 at 4:40 am

    I am getting this exact error but I am not sure how to get into do I get into wp-config.php which is located in the root WordPress directory as I don’t know where to find it. Yes I am a complete beginner. Can you help?

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in /home/crooked1/public_html/wp-includes/SimplePie/Sanitize.php on line 331

    Odpowiedz

    • WPBeginner Support

      sty 13, 2014 at 4:34 pm

      How to use FTP to upload WordPress.

      Odpowiedz

      Admin

11. mike .levine

    gru 20, 2013 at 2:40 am

    Thank you so much!! For real.. you have been a lifesaver. I can’t tell you how appreciative I am for your help.

    Odpowiedz

12. Timothy

    gru 9, 2013 at 8:00 am

    Hi,

    I’ve tried to increase the limit to 64mb, and I got this warning until 5 times:

    ‘WARNING: Job restart due to inactivity for more than 5 minutes.’

    The database backup is stopped until 60s%, and the result is below when it tried to upload to Dropbox:

    ‘ERROR: Uploaded file size and local file size don’t match.’

    What’s wrong with it? I’m using Bluehost.

    Thanks!

    PS: I’m not a technical person, so give explanation in details

    Odpowiedz

13. Thomas Cole

    gru 5, 2013 at 1:04 am

    Been having a doozy of a time working on my site and I would sacrifice a MacBook at midnight to get my site working, one little line of code and we are back up. Thanks!

    Odpowiedz

14. Domestic Herald

    wrz 30, 2013 at 12:00 pm

    THANK YOU so much!!!! This worked like a charm and took me less than a minute to implement.

    Odpowiedz

15. Jonni

    wrz 18, 2013 at 1:19 pm

    Thank you so much!!!!
    I’m in the middle of a launch and all of a sudden I couldn’t update or create any web pages on the whole site because of a 500 Internal Server Error. (And of course this happened as soon as I discovered the Home page had a big problem.)

    Could get no help from support, am not a web developer.

    Yet I was STILL able to follow your instructions and Hallelujah! Miracle of Miracles! Everything works now.

    All this work driving traffic, getting new people to the site – almost wasted due to server error – but Disaster Averted! you saved the day.

    My sincerest gratitude.

    Again, can’t thank you enough.

    Odpowiedz

16. bungkelip

    wrz 11, 2013 at 11:27 am

    I add define(‘WP_MEMORY_LIMIT’, ‘1024M’); but its not work, help me

    Odpowiedz

17. Casey Friday

    sie 20, 2013 at 6:26 pm

    Thanks so much! I was about to bitch to WooThemes that their $129 extension was breaking my site, but it turned out to be a memory issue. Cheers!

    Odpowiedz

18. Janelle

    sie 20, 2013 at 4:37 pm

    Thanks a million! This is so useful, and more people should see this post.

    Odpowiedz

19. Adrian

    sie 8, 2013 at 1:49 pm

    On line 36/37 of wordpress, wp-config.php you must type:

    /** Memory Limit */
    define(‘WP_MEMORY_LIMIT’, ’64M’);

    For me this problem is solve thi way. You can change 64M with what value you want.

    Odpowiedz

    • Adam Singer

      wrz 23, 2013 at 3:46 pm

      This comment is sooo key!

      You have to add define( ‘WP_MEMORY_LIMIT’, ’64M’ ); just before the unique key and salts are defined, otherwise the change doesn’t take effect. Thanks!!!

      Odpowiedz

      • omniafausta

        kwi 28, 2014 at 8:36 am

        yesssss thanks, I was wondering why it didn’t work for me. It was because so far no one told me WHERE in the wp-config i had to add this line. THANKS!!!

        Odpowiedz

    • Rosie Taylor

      maj 30, 2014 at 12:39 am

      Thank you for clarifying this step. Now I know why it never just changing the other line for the value didn’t work before. This saved me big time for a client tonight!

      Odpowiedz

20. Titel

    sie 3, 2013 at 6:22 am

    Hello,
    Today I had a problem with wordpress: after I logged appeared “white screen of death”. We went into cpanel and inserted “define (‘WP_MEMORY_LIMIT’, ’64M ‘)’ in wp-config.php and everything went very well.
    Thanks a lot WPBeginner.

    Odpowiedz

21. Hamza Ahmed

    lip 28, 2013 at 9:24 am

    Thanks a lot, i work very hard with every method i found on internet, but i filled , my problem occur during word-press installation i pasted this code in mid and increase its value to 128 mb , now its works fine, thanks a lot again.

    Odpowiedz

22. Jeff Danforth

    maj 30, 2013 at 12:12 pm

    My host provides 64MB, and wants a hefty kicker to increase the php memory limit – so I’m inclined to be “green” and reduce my memory use.

    HOW might I determine what plugins or other things to remove to stay under 64MB
    A) php memory consumption, e.g. which plugins are being greedy
    B) have I got a memory leak issue, e.g. any plugins being nasty

    Thank you for this forum, by the way – I am truly a beginner, but excited about WP (grrr, if I can make it jump its hoops right)

    Odpowiedz

23. Matthew

    maj 28, 2013 at 3:25 pm

    This worked for me, thanks for the tip!

    Odpowiedz

24. Daniel

    maj 19, 2013 at 7:06 pm

    Didn’t work for me, but I’m not sure what it means to be “inside the main php tag”. I opened the file in Dreamweaver and did a search. The word “main” doesn’t appear anywhere on the page. So I put the code in line 2, just after the “<php". Tried it at 64 and 128. Thanks.

    Odpowiedz

    • Editorial Staff

      maj 22, 2013 at 7:32 am

      The main php tag means just insert it like you did. Sometimes this doesn’t work in which case you have to ask your host.

      Odpowiedz

      Admin

25. Deepanshu

    kwi 27, 2013 at 12:19 pm

    Thanks for the help.
    But 64M was already default for me and of course it wasn’t sufficient so I changed it to 96M and I think u should mention this as well.

    Odpowiedz

26. Jan

    kwi 19, 2013 at 4:43 am

    Nice but nothing works – use rackspace cloud – tried 32 – 64 – 128 – 256- 512 – 1024Mb MU site i can’t go more up and only in admin i can’t get access after a plugin from wpmudev so guess i have to delete that and try something pro.

    Odpowiedz

27. Julie Geiger

    kwi 18, 2013 at 1:39 pm

    worked perfect.. thank you for sharing, tried a few other fixes but all errored out.

    Odpowiedz

28. Nick

    kwi 18, 2013 at 3:28 am

    Thank you for the article. It was a great help

    Odpowiedz

29. pathik

    kwi 12, 2013 at 9:03 am

    its really work,, i had problem of internam server,,, when add new plugine,,, i just increse memomry limit
    define(‘WP_MEMORY_LIMIT’, ’64M’);
    in wp-admin and problem solved..

    tthnaks a lot

    Odpowiedz

30. Joke van de Fliert

    mar 11, 2013 at 5:46 am

    thanks! for me the provider had to change a setting to increase the memory limit, but that did fix it!

    Odpowiedz

31. Jennifer Ortiz

    paź 26, 2012 at 11:55 am

    Thanks a million for this! I got the error message right after the WordPress install–I never even had a chance to add a plug-in.:

    Fatal error: Allowed memory size of 33554432 bytes exhausted…

    All seems to be working fine now.

    Odpowiedz

32. Timothy Jacobs

    lut 29, 2012 at 9:44 pm

    I have tried to do this, but it has not solved the problem.  I am on 1&1 hosting and I have tried all the changes, but I still get this error whenever uploading a semi-large picture:
     
    Fatal error: Out of memory (allocated 29884416) (tried to allocate 4096 bytes) in /homepages/21/d258522816/htdocs/TBJFilms/WP/wp-includes/media.php on line 1010
     
    What is your suggestion?

    Odpowiedz

    • wpbeginner

      mar 1, 2012 at 12:37 am

       @Timothy Jacobs Contact your host. If they refuse to help, then switch.

      Odpowiedz

33. aidilgoh

    wrz 26, 2011 at 2:10 pm

    Tried placing this at the end of the wp-config.php and didnt work.

    However, placing it on top right after the <?php tag worked. Hooray!

    Odpowiedz

    • Guy

      wrz 14, 2012 at 6:13 am

      Exactly !! thanks a lot – made my day !

      Odpowiedz

    • Appdunia

      kwi 27, 2013 at 2:27 pm

      Worked for me only after placing just after php tag. Thanks a lot !

      Odpowiedz

    • Ahmad Zaruq Spain

      sie 10, 2014 at 7:26 pm

      Yes, I used the
      1error_reporting(E_ALL); ini_set(‘display_errors’, 1);
      2
      3define( ‘WP_DEBUG’, true);I found in a post next to this one and was getting an error by using define(‘WP_MEMORY_LIMIT’, ‘128M’); on the last line of my php-config file. Thanks to this comment I placed it right below <?php tag at the top and now the error report is no longer I just hope my site doesn't keep crashing on every new plugin install, going to check that now. Thanks to all you geeks out there!

      Odpowiedz

34. PatrickTyrus

    sie 1, 2011 at 10:49 am

    this was a great help, but as you noted it could easily be a plugin, or as someone mentioned it could be a memory leak.

    And as others have pointed out, there are memory settings for a reason, some hosts will cut your services if you try to circumvent them.

    Is there a way to check on what’s eating memory?

    I’ll be searching, but this is something that should be listed under related posts, or as a note and link at the end regarding one of the “numerous solutions for it”. Going for the “simplest one” might get you through the day, but is may not be a good long term solution as it may cover up the real problem and delay the inevitable.

    Odpowiedz

    • Alexis O'Neill

      mar 8, 2015 at 12:36 pm

      Worked for me!! I changed my site language to Spanish and I guess that used up the memory. Added the simple line recommended in the post and voilá!! Back in my admin mode. The really helpful part was “Don’t panic!” because my anxiety level was rising fast.
      Thanks ever so much.

      Odpowiedz

    • Kiu Karakas

      mar 10, 2015 at 11:50 am

      define(‘WP_MEMORY_LIMIT’, ’64M’);
      not solved
      define(‘WP_MEMORY_LIMIT’, ‘164M’);
      solved
      THANKS

      Odpowiedz

35. wpbeginner

    maj 30, 2011 at 12:56 am

    @shally1584 There is no = << in our code. So are you sure that you are pasting our code as an independent function and not as part of something else.

    Odpowiedz

36. shally1584

    maj 30, 2011 at 12:54 am

    hi.i tried to adjust memory limit and got this error

    ‘Parse error: syntax error, unexpected ‘=’ in /home/amanerdm/public_html/beaverealty.com/wp-config.php on line 62′

    pls help fix this.thanx.

    Odpowiedz

37. Luna

    mar 22, 2011 at 3:28 pm

    Thank you for this post… I had a couple of category / archive query pages that were throwing this error after I upgraded to WordPress 3.1. I was just about to re-write the queries until I found your post in a Google search.

    You saved me a lot of work and headaches

    Odpowiedz

38. Kdb

    mar 3, 2011 at 10:46 am

    I ended up having to switch hosting companies because I couldn’t get my current one to increase the memory from 32MB to, well, anything more. Pretty sad. Took a bit of hassle to transfer three WordPress sites (and multiple other sites), but it was worth it. My current host offers 128MB and my sites are working SO much better. I can actually add plug-ins.

    Odpowiedz

39. Richard

    mar 2, 2011 at 10:17 am

    Hello
    I tried the fix by adding the line immediately after the opening >php tag (line 1)
    define(‘WP_MEMORY_LIMIT’, ’64M’);

    It did not work for me BUT
    I placed the line with comments for my own use on (as it happens) line 22 and it worked.

    I am testing this procedure on a test WP site using Twentyten 1.2 Theme

    /home/par*****/public_html/wp-config.php

    Line 22 /** WP memory limit Note it does not work when placed immediately after line 1 */
    define(‘WP_MEMORY_LIMIT’, ’64M’);

    Odpowiedz

40. Chris

    sty 29, 2011 at 7:53 am

    This trick doesn’t work for me ever since WP 3.

    what I found worked was to create a PHP.INI file in the wp-admin folder with the line:

    memory_limit = 128M

    (or whatever you want to make it)

    Odpowiedz

    • Editorial Staff

      sty 30, 2011 at 5:33 pm

      Sounds like a host issue rather than WP 3.0 issue. We still have this trick working on our clients.

      Odpowiedz

      Admin

      • Trunks

        lut 13, 2011 at 10:55 pm

        This worked for me! Thanks!!!

        Create PHP.INI in the wp-admin folder, with the line “memory_limit = 128M;”

        I changed all the other methods, and this was the only one that seemed to work.

        Odpowiedz

        • Don

          maj 24, 2014 at 4:31 pm

          Thanks. This worked for me! Nothing else worked until I read your comment. Website host was not overly helpful.

    • dan

      lut 21, 2013 at 7:02 am

      Brilliant! Thanks!

      Odpowiedz

41. kdb

    gru 8, 2010 at 3:05 pm

    I tried this, but my host limits it to 32 megs. Can anyone recommend a good host for WP, because I’m going to have to change. Thanks!

    Odpowiedz

    • Editorial Staff

      gru 9, 2010 at 7:16 am

      Look through our list of recommended hosts. You can find it on our homepage.

      Odpowiedz

      Admin

42. phil

    lis 15, 2010 at 8:58 pm

    I put that line at the very top of the file (wp-config.php) and it worked!

    Odpowiedz

43. ayahshiva

    paź 10, 2010 at 10:32 pm

    i also got the same warning when i activated too many plugin

    Odpowiedz

44. Eyl

    lip 5, 2010 at 7:12 am

    I have done the trick but seems like nothing happened. The error keep showing so can you suggest other solutions?

    Odpowiedz

    • Editorial Staff

      lip 5, 2010 at 6:47 pm

      On some hosts, this trick won’t work. So you have to ask (beg) them to increase the PHP Memory Limit. OR get rid of the plugin which is causing it.

      Odpowiedz

      Admin

45. Seth Merrick

    kwi 1, 2010 at 10:27 pm

    Great article. A brand new plugin that may soon find its way on to this list is Cobalt WP Boost.

    Check it out here:
    http://frugaltheme.com/about/cobalt-wp-boost-plugin/

    It allows blog owners to raise their WordPress Memory Limits with a couple of mouse clicks, as well as showing at-a-glance memory usage information. WordPress keeps its internal memory limit at 32MB, which is fine for a small-time blog; but if you’re trying to add any robust plugins for social networking or ecommerce applications, 32M will not suffice. This problem can only be expected to worsen with the release of 3.0 which, judging from the beta release, will consume a lot more memory itself without upping the 32MB limit.

    Odpowiedz

    • Chad McCullough

      kwi 2, 2010 at 6:23 am

      I just downloaded the plug-in and I’ll give it a try on my test site. Thanks.

      Odpowiedz

46. W^L+

    mar 23, 2010 at 5:12 pm

    Just remember that if the problem is a memory leak (either in PHP itself or in some library that is used by a plugin), this will merely delay the occurence.

    Before you change the memory limits, you should ensure that you’re using the most up-to-date versions of any plugins. Be sure you are running the newest version of WP. If your host offers multiple versions of PHP, be sure you’re using version 5.

    Your hosting service may have preset limits on memory usage. If your editing causes you to exceed those limits, your service may be suspended or canceled without warning.

    Odpowiedz

    • Dunn

      sty 6, 2011 at 4:17 am

      I tried to deactivate the plugins one by one and found out that the Google XML Sitemaps plugin cause problem.

      Odpowiedz

47. Muhammad Asad

    mar 23, 2010 at 8:28 am

    I would like to try it! Thanks for the trick.

    Odpowiedz

48. wparena

    mar 22, 2010 at 9:17 am

    I think the better way is to put this limit in wp-setting.php file where this memory limit already described as 32M, just changed that value to 64M.

    Odpowiedz

    • Chad McCullough

      mar 22, 2010 at 9:39 am

      Thank you, wparena. I’ll try this.

      Odpowiedz

    • Chad McCullough

      mar 22, 2010 at 9:53 am

      Changing the settings in the wp-settings.php file fixed my 2 week, driving me crazy, issue! Thank you very much!!

      -Chad

      Odpowiedz

    • Editorial Staff

      mar 22, 2010 at 10:58 am

      Yes, but editing the core files is not the best way. You would have to change that every time you update WordPress. The way we share in this article, will save you time.

      Odpowiedz

      Admin

      • Chad McCullough

        mar 22, 2010 at 11:04 am

        I would much rather not modify core files, if possible. Where would I place the line in the wp-config.php file? I’m not sure where the main php table is.

        Thanks for the article and the help!

        Odpowiedz

        • Editorial Staff

          mar 22, 2010 at 12:48 pm

          Place it right after the table prefix

        • Chad McCullough

          mar 22, 2010 at 3:41 pm

          That worked. Thanks!

49. Kate Mag

    mar 22, 2010 at 8:38 am

    Awesome trick. Is that same with PHP memory limit?

    Odpowiedz

50. Chad McCullough

    mar 22, 2010 at 8:36 am

    I think that this might fix an issue I’ve been having with my site. I just can’t figure out where the main php table is in the wp-confip.php to place the line.

    Thanks!

    Odpowiedz