WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

#12057 closed defect (bug) (fixed)

Allowed memory exhausted in 3.0-alpha

Reported by: adamtaylor Owned by: dd32
Milestone: 3.0 Priority: normal
Severity: normal Version: 3.0
Component: Filesystem API Keywords:
Focuses: Cc:

Description

I svn up'd to 3.0-alpha the other day and have noticed on the dashboard two small errors:

The plugins box is showing the following error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 44247 bytes) in /var/www/adamjctaylor.com/trunk/wp-includes/wp-db.php on line 536

and the wordpress development blog box is showing a similar error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 38233 bytes) in /var/www/adamjctaylor.com/trunk/wp-includes/functions.php on line 944

Some environment info:

It's running on Debian and the full phpinfo() output can be seen here:

http://www.adamjctaylor.com/i.php if that helps...

If any other information is useful I'm adam-_- on irc and I'll try and keep on an eye on the ticket for a while (if I remember).

Cheers

Change History (13)

comment:1 nacin4 years ago

Running trunk earlier, I saw some memory issues as well running the default 32M allocation, though I attributed it as just a hiccup.

For reference, wp-db:536 is mysql_real_escape_string() in (this is also where I had errors) and functions.php:944 a call to serialize() in maybe_serialize().

comment:2 scribu4 years ago

  • Milestone changed from Unassigned to 3.0

comment:3 ocean904 years ago

  • Keywords reporter-feedback added; memory removed

adamtaylor: As I can see on your phpinfo your memory_limit is only 16M. It should be 32M by default. Can you increase it and test again?
I didn't get memory issues with 32M in trunk/3.0-beta.

comment:4 dd324 years ago

Have traced most of this problem down, just waiting for confirmation that the suggested fix will fix it.

comment:5 dd324 years ago

  • Keywords reporter-feedback removed

comment:6 dd324 years ago

  • Owner set to dd32
  • Status changed from new to accepted

comment:7 dd324 years ago

(In [14120]) Return false on WP_Filesystem_FTPext::dirlist() for non-existant folders. See #12232. See #12057

comment:8 dd324 years ago

  • Component changed from General to Filesystem

comment:9 dd324 years ago

Has that fixed it for anyone affected? You'll need to copy a new copy of wp-admin/includes/class-wp-filesystem-ftpext.php over manually, or SVN up first.

comment:10 ocean904 years ago

  • Keywords reporter-feedback added

comment:11 adamtaylor4 years ago

I svn up'd and that message has been replaced by:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 30720 bytes) in /var/www/adamjctaylor.com/trunk/wp-includes/class-simplepie.php on line 14106

So I suppose one has been fixed an another bug is now present? Or should I just increase the allowed memory of PHP?

comment:12 scribu4 years ago

  • Keywords reporter-feedback removed

comment:13 ocean904 years ago

  • Resolution set to fixed
  • Status changed from accepted to closed

The original issue is fixed.
Memory limit should be 32M.

Note: See TracTickets for help on using tickets.