Make WordPress Core

Opened 14 years ago

Last modified 14 years ago

#14205 closed defect (bug)

Out of Memory Errors: /wp-includes/query.php — at Version 2

Reported by: resellr's profile Resellr Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Query Keywords:
Focuses: Cc:

Description (last modified by dd32)

VPS SOFTWARE:

PHP 5.3.x
MySQL 5.1.x
Apache 2.2.x
xCache 1.3.x
Suhosin & SuPHP

VPS SPECIFICATIONS:

3.2GHz Dedicated CPU
2GB Dedicated RAM
CentOS 5.x

xCache is given 48MB of RAM as Dedicated. PHP max. memory has been raised from 32MB to 64MB (we've tested it both ways).

That said, we've commented out the standard Apache Configuration limits on CPU & RAM prior to submitting this ticket (we saw this in a previous ticket, so http.conf has already been modified).

The issue here is that we're experiencing timeouts when trying to save any large amount of Text, PHP or CSS through the WordPress Admin Interface.

If we exceed the size of the box (non-modifed, non-extended), it times out and the following error is logged:

PHP Fatal error: Out of memory (allocated 6291456) (tried to allocate 491520 bytes) in /home/username/public_html/wp-includes/query.php on line 1906

Line 1906 is:

		if ( !empty($q['category__not_in']) ) {
			$cat_string = "'" . implode("', '", $q['category__not_in']) . "'";
			$whichcat .= " AND $wpdb->posts.ID NOT IN ( SELECT tr.object_id FROM $wpdb->term_relationships AS tr INNER JOIN $wpdb->term_taxonomy AS tt ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy = 'category' AND tt.term_id IN ($cat_string) )";
		}

That doesn't really make the most sense to me, seeing as how it relates to categories, not the saving of a file.

Change History (2)

#1 @nacin
14 years ago

  • Keywords reporter-feedback added; query.php oom out of memory removed

6291456 bytes is 6 MB. WordPress hums along, without any plugins or a localization loaded, at anywhere from 12-17 MB, and attempts to assign itself a limit of 32 MB (which arguably should be 48 MB) during startup. Most likely, that action is blocked, and your server isn't configured properly, giving the script much less than it requires.

#2 @dd32
14 years ago

  • Description modified (diff)
  • Keywords close added

Suhosin can limit memory as well, check the settings on that.

That being said, Given the script is only allocated 6MB at that point in this, This is a invalid ticket as WordPres ssimply required more memory than that.

Note: See TracTickets for help on using tickets.