• Hi,

    I upgrades from 2.2.1 to 2.2.2 this morning and I cannot do anything any more. I receive one of those messages :

    Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 148837 bytes) in /home/www/c470c87ded1bc91f3e2e84eb4ade04d0/web/wp-principal/wp-includes/streams.php on line 58

    After reading the posts regarding this kind of error, I cannot figure out a solution. So I tried to go back to the previous version of my site. I copied all the wp files back and I also import the backup of my database. But the problem remains.

    Further I still can access another wordpress 2.2.1 that I put in another folder on the same server for tests purpose.

    What can I do to recover my site ?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Hello. Same here but on new install.

    I had WordPress staff install WP for me last night.(install4free WordPress)

    On trying to use it ( administer site / view plugins / change theme )I keep getting following error message.

    “Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 35 bytes) in /home/sites/********/public_html/wordpress/wp-admin/admin-functions.php on line 1734”
    Any ideas anyone? ??

    Many thanks. ??

    Thread Starter boreal123

    (@boreal123)

    Hello,

    Before to perform the upgrade, I deactivate my plugins. Anyway, now I have no more access to the admin console. Is there a way to check if there are some plugins left activated ?

    Furthermore, I went back to the previous version and the problem is still here, even with the old version that used to run this morning.

    The file who raise the error message is “streams.php”

    Did you even look at the link that whooami provided. There are hundreds of posts about the same thing and most all of them are the same solution. Get your host to increase your php memory limit. The problem is that your web server ran out of memory to execute the wordpress scripts and can’t get more hence getting your host to increase the limit.

    Thread Starter boreal123

    (@boreal123)

    Yes, I read all those links and I also noticed that whoami posted the same answer lots of times during the last months.

    Unfortunately, I cannot receive more memory than 16 Mb (the problems seams to happen for people with a limit of 8 Mb and even for one with 128 Mb).

    Is there a way to be sure that the plugins are all deactivated directly inside the database ?

    Tell your host to restart your web server that might clear up the issue for right now and allow you to get back into your wordpress and cut down on the plugins you use.

    Thread Starter boreal123

    (@boreal123)

    Ok, I’ll phone them, but I not sure they will be happy with this because it’s a mutualised server…

    I also had this problem. But, I noticed that wasn’t because of plugins. That was from wp_option’s data. If you have that problem, First, delete rss_*,records in wp_options table.
    and disable sources to get recent rss data on dashboard.

    Thread Starter boreal123

    (@boreal123)

    As supposed, my host will not restart the server on which is my website. Further, they say, with no surprise, that WP is running fine on their test platform that has no memory limitation. And therefore, they let me find a solution within the WP files.

    Any idea ?

    I will also try the proposal from elpis2000.

    Thread Starter boreal123

    (@boreal123)

    Hi,

    As I thought, my web host did not agree with restarting the server. But they performed a few tests.

    They said that when the function read($bytes) is called, the $byte contains a huge value. This seems to be linked with the language package I used (fr_FR.mo).

    So I simply fall back on an old version of the site without the language package and it worked. But now, I am not confident at all in upgrading the site anymore…

    Same problem here:

    Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 33 bytes) in C:\xampplite\htdocs\WordpressCN\wp-admin\import\wordpress.php on line 88

    I have increased php.ini memory allocation to 32MB but to no avail ??

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Memory problems after upgrading to 2.2.2’ is closed to new replies.