{"id":6011,"date":"2020-04-01T15:00:35","date_gmt":"2020-04-01T13:00:35","guid":{"rendered":"https:\/\/qodeinteractive.com\/magazine\/?p=6011"},"modified":"2020-10-26T17:00:51","modified_gmt":"2020-10-26T16:00:51","slug":"allowed-memory-size-of-bytes-exhausted-error","status":"publish","type":"post","link":"https:\/\/qodeinteractive.com\/magazine\/allowed-memory-size-of-bytes-exhausted-error\/","title":{"rendered":"How to Fix the “Allowed Memory Size Of Bytes Exhausted” Error in WordPress"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text]WordPress is the world\u2019s most popular platform for content creation and management, especially for users with little to no coding background. Yet no matter how simple it is, sooner or later you will stumble upon a WordPress error. The troubleshooting for the errors may vary, but most of them have one thing in common – you can quickly find a solution<\/strong>.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Luckily, Allowed Memory Size Of Bytes Exhausted Error is one of those tame issues, with quite an easy and intuitive solution. Its error message reads: \u201cAllowed memory size of X bytes exhausted (tried to allocate Y bytes) in your-site\/some-file-path on line Z,\u201d with X, Y, Z displayed as numbers.[\/vc_column_text][vc_empty_space height=”50px”]

\n
\n \"Memory <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]The error is caused by a lack of available server memory<\/strong>, mostly due to an overuse of plugins. We\u2019ll show you how to tackle this issue by breaking it down into several smaller steps.[\/vc_column_text][vc_empty_space height=”68px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n

Solving the Error<\/h2>\n

[\/vc_column_text][vc_column_text]Due to the cause of the error, two possible solutions immediately come to mind \u2013 deactivating unnecessary plugins and increasing the memory_limit <\/em>parameter<\/strong>.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Before you proceed with troubleshooting, it is strongly recommended to create a backup of your WordPress site<\/a>. You can do it manually or contact your hosting provider to help you.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Another tip before we start – wait a couple of minutes and try to refresh the page<\/strong>, just to make sure the error isn\u2019t only temporary.[\/vc_column_text][vc_empty_space height=”72px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n

Deactivating Plugins<\/h3>\n

[\/vc_column_text][vc_column_text]Disabling plugins is the easier and quicker of the two possible solutions to the issue. Navigate to Plugins > Installed Plugins<\/em>, find a plugin and deactivate it<\/strong>. Clear the browser cache and reload the page<\/strong>. Repeat the process until the error is gone. We strongly suggest you keep these plugins deactivated.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]However, if the error isn\u2019t solved or some plugins are too valuable to be deactivated, proceed to the second solution.[\/vc_column_text][vc_empty_space height=”72px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n

Increasing Server Memory<\/h3>\n

[\/vc_column_text][vc_column_text]Before we discuss the ways to increase server memory, here are a few important things you need to know.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]First, increasing memory is only<\/strong> possible within the limits of your hosting package<\/strong>. If 256M isn\u2019t enough, using higher values will likely result in a 500 internal server error. Consult with your hosting provider about the change, especially if you are using shared hosting.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Second, in order to perform the changes described in this guide, you will have to edit files using an FTP client<\/a>. If you don\u2019t feel comfortable doing this, ask your hosting provider to help you.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Now we will show you 4 methods for increasing the memory_limit<\/em><\/strong>. After implementing each of the following solutions and prior to running the test, don\u2019t forget to clear the browser cache<\/strong>.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Onto the solutions![\/vc_column_text][vc_empty_space height=”81px”][vc_separator color=”custom” accent_color=”#f0f0f0″][vc_empty_space height=”50px”][vc_widget_sidebar sidebar_id=”top-picks-banner”][vc_empty_space height=”28px”][vc_separator color=”custom” accent_color=”#f0f0f0″][vc_empty_space height=”70px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n

    \n
  1. Editing\u200c the \u200cwp-config.php\u200c \u200cfile\u200c<\/strong><\/li>\n<\/ol>\n

    [\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]To edit the wp-config.php<\/em> file, connect to the server using your FTP credentials<\/strong>. Navigate to the root WordPress directory and find the wp-config.php<\/em> file.[\/vc_column_text][vc_empty_space height=”50px”]

    \n
    \n \"WP <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]Edit the file using a text editor. Simply add the following line of code<\/strong> before the \/*<\/em> That’s all, stop editing! Happy blogging. *\/<\/em> line.[\/vc_column_text][vc_empty_space height=”50px”][vc_column_text]<\/p>\n
    define( 'WP_MEMORY_LIMIT', '256M' );<\/pre>\n
    [\/vc_column_text][vc_empty_space height=”39px”]
    \n    
    \n                                    \"Wp                        <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]Save the changes and upload the edited file<\/strong> to the same place where the original file was located. This action will override the old file.[\/vc_column_text][vc_empty_space height=”28px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n
      \n
    1. Editing the php.ini file<\/strong><\/li>\n<\/ol>\n
      [\/vc_column_text][vc_column_text]The php.ini<\/em> file is also located in the root WordPress directory, so you can access it the same way as the wp-config.php<\/em> file.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Open the file with a text editor, search for memory_limit<\/em> and change the value associated with it<\/strong>. Similarly, save the changes and override the old file with the new one.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]If there is no file, create it and insert this line of code.[\/vc_column_text][vc_empty_space height=”50px”][vc_column_text]<\/p>\n
      memory_limit = 256M<\/pre>\n
      [\/vc_column_text][vc_empty_space height=”18px”][vc_column_text]For some shared hosts, you have to specify your root WordPress directory in order for the memory limit increase to take effect<\/strong>. You can do this by adding the following code to your .htaccess<\/em> file, near the top.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]Change the \u201cyour_username\u201d part with your actual cPanel username.[\/vc_column_text][vc_empty_space height=”50px”][vc_column_text]<\/p>\n
      <IfModule mod_suphp.c> \r\nsuPHP_ConfigPath \/home\/your_username\/public_html\r\n<\/IfModule><\/pre>\n
      [\/vc_column_text][vc_empty_space height=”18px”][vc_column_text]Edit the .htaccess<\/em> file using a text editor. You can find more details about accessing the .htaccess<\/em> file in Section 4, where we describe the fourth solution to this error.[\/vc_column_text][vc_empty_space height=”50px”]
      \n    
      \n                                    \"Htaccess                        <\/div>\n<\/div>[vc_empty_space height=”38px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n
        \n
      1. Changing the cPanel options<\/strong><\/li>\n<\/ol>\n
        [\/vc_column_text][vc_column_text]Another way to solve the error is to change the memory limit value within the cPanel<\/strong>. Login to cPanel using your credentials, navigate to the Software<\/em> section, and click on the \u201cMultiPHP INI Editor\u201d.[\/vc_column_text][vc_empty_space height=”50px”]
        \n    
        \n                                    \"cPanel                        <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]Select your domain from the dropdown list, search for the \u201cmemory_limit\u201d attribute, and insert 256M as the respective value.[\/vc_column_text][vc_empty_space height=”50px”]
        \n    
        \n                                    \"cPanel                        <\/div>\n<\/div>[vc_empty_space height=”60px”]
        \n    
        \n                                    \"cPanel                        <\/div>\n<\/div>[vc_empty_space height=”38px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n
          \n
        1. Editing the .htaccess file<\/strong><\/li>\n<\/ol>\n
          [\/vc_column_text][vc_column_text]Finally, you can solve the error by editing the .htaccess<\/em> file. This file is also found in the root WordPress directory. It is a server configuration file and usually hidden<\/strong>.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]To access it, you should enable the relevant option(s) for showing hidden files within the FTP client of your choice. If you use FileZilla, as we do, navigate to the Server tab and click on \u201cForce showing hidden files\u201d.[\/vc_column_text][vc_empty_space height=”50px”]
          \n    
          \n                                                            <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]Connect to the server using your FTP credentials, navigate to the root WordPress directory, and find the .htaccess<\/em> file.[\/vc_column_text][vc_empty_space height=”50px”]
          \n    
          \n                                    \"Htaccess                        <\/div>\n<\/div>[vc_empty_space height=”38px”][vc_column_text]Open the file, search for \u201cmemory_limit\u201d and change the value<\/strong> associated with it. Save the changes and override the old file with the new one.[\/vc_column_text][vc_empty_space height=”28px”][vc_column_text]If there is no code present, insert this line.[\/vc_column_text][vc_empty_space height=”50px”][vc_column_text]<\/p>\n
          php_value memory_limit 256M<\/pre>\n
          [\/vc_column_text][vc_empty_space height=”39px”]
          \n    
          \n                                    \"Htaccess                        <\/div>\n<\/div>[vc_empty_space height=”79px”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n
          Final Thoughts<\/h2>\n
          [\/vc_column_text][vc_column_text]Using any of these methods to fix the Allowed Memory Size Of Bytes Exhausted Error takes only a few minutes. On top of showing you how to solve this issue, we\u2019ve also tried to shed light on the sources of this problem. With this guide, not only are you better equipped for dealing with unexpected errors, but you\u2019re also more knowledgeable about the way your website works. [\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"
          Learn how to fix the allowed memory size of bytes exhausted error in WordPress like a pro. Follow our guide and find out how to increase your memory.<\/p>\n","protected":false},"author":11229,"featured_media":8031,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[4,52,13],"class_list":["post-6011","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-tips","tag-troubleshooting","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts\/6011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/users\/11229"}],"replies":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/comments?post=6011"}],"version-history":[{"count":0,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts\/6011\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/media\/8031"}],"wp:attachment":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/media?parent=6011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/categories?post=6011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/tags?post=6011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}