Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#5399 closed defect (bug) (invalid)

WordPress 2.3.1 seems more prone to exhaust PHP memory on XMLRPC upload

Reported by: redsweater Owned by: josephscott
Milestone: Priority: normal
Severity: normal Version: 2.3.1
Component: General Keywords:
Focuses: Cc:

Description (last modified by josephscott)

I have started noticing a trend in reports from users who have updated to 2.3.1 and are suddenly noticing image upload failures with errors that implicate PHP running out of memory. A workaround for the problem has been to have server configurations altered to increase memory allotment for PHP, but not all users' server administrators are willing to make this change.

I'm curious as to whether this is a case of WordPress just "using a little more memory" and pushing the high water mark such that this problem is more likely to happen, or whether it's a case of it using a LOT more memory when processing XML, and thus something that needs to be seriously investigated.

A forum post on my site describes one of the error cases:


And I noticed this one indicating the problem has also been observed on Ecto:


I'm not sure this is really a problem with WP, or even 100% sure that the problem actually corresponds with something that changed in 2.3 -> 2.3.1, but the trend seems to suggest something along those lines.


Change History (7)

comment:1 JeremyVisser6 years ago

Memory usage seems to have gone up with 2.3. I'm not aware of it becoming higher in 2.3.1.

This higher memory usage irks me a little, especially seeing as though you can no longer install WP 2.3 on a host that has 8M set as its memory_limit — Doteasy.com comes to mind straight away (although they will happily increase the limit if you contact support).

comment:2 darkdragon6 years ago

I've noticed this, and it seems quite interesting. I want to run some tests as I think WordPress is causing a lot of load and memory usage on my host.

The testing would have to be difficult and time consuming. However I think just setting up a Test WordPress blog and visiting while using XDebug should point out areas that need to be looked at.

Should any patches on the matter be submitted to this ticket?

comment:3 darkdragon6 years ago

Nevermind. Will have to create a new ticket for fixing any other memory and/or issues.

comment:4 DD326 years ago

Related; See This ticket/changeset:

(In [6681]) Increase memory limit. Props darkdragon. see #3141

It attempts to increase the memory_limit to 32M for 2.4/2.5 if possible,
Else no change is made.

Optimizations still need to be made to decrease memory usage in high-usage areas however.

comment:5 santosj6 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Not a WordPress issue. Version 2.5 should help with this, if not then you can increase the memory limit in PHP configuration or in wp-config.php.

comment:6 santosj6 years ago

  • Milestone 2.9 deleted

comment:7 josephscott5 years ago

  • Description modified (diff)

For others who may find this ticket in the future, work is being done on reducing the memory usage for large XML-RPC requests. See ticket #10698

Note: See TracTickets for help on using tickets.