[wp-trac] [WordPress Trac] #14205: Out of Memory Errors: /wp-includes/query.php

WordPress Trac wp-trac at lists.automattic.com
Tue Jul 6 06:17:38 UTC 2010


#14205: Out of Memory Errors: /wp-includes/query.php
--------------------------+-------------------------------------------------
 Reporter:  Resellr       |       Owner:                         
     Type:  defect (bug)  |      Status:  new                    
 Priority:  normal        |   Milestone:  Awaiting Review        
Component:  Query         |     Version:  3.0                    
 Severity:  normal        |    Keywords:  reporter-feedback close
--------------------------+-------------------------------------------------
Changes (by dd32):

  * keywords:  reporter-feedback => reporter-feedback close


Old description:

> 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.

New description:

 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.

--

Comment:

 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.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14205#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list