[wp-trac] [WordPress Trac] #6894: 2.5.1 only - some post text (persian) causes timeout on publish (not save)

[WordPress Trac]

#6894: 2.5.1 only - some post text (persian) causes timeout on publish (not save)
----------------------------+-----------------------------------------------
 Reporter:  jeremyclarke    |       Owner:  anonymous
     Type:  defect          |      Status:  new      
 Priority:  high            |   Milestone:  2.5.2    
Component:  Administration  |     Version:  2.5.1    
 Severity:  critical        |    Keywords:           
----------------------------+-----------------------------------------------
 I run a set of translations of our sites main english content. I recently
 upgraded each of the translation wp installs from 2.3.3 to 2.5.1 and it
 went great for almost all the languages.


 For some reason the Persian/Farsi version is having insane problems
 publishing. Some content will go through fine, but if certain characters
 are present any attempt to publish the post causes cpu to go up to 100%
 (using top through ssh) and hang until php times out (I tried 30s and 60s
 timeouts, made no difference, it is a powerful new quadcore server with a
 seperate quadcore db server, so it's definitely not a lack of resources).


 If you want to test this on your install you can use this text as an
 example
  http://pastie.caboo.se/189915
 (put the text below TITLE as the title and the text below CONTENT as the
 post content), you probably can't read it but it's just some normal Farsi
 text (i can't read it either). My database is utf8_unicode_ci (also tested
 on utf8_persian_ci), which you'll need to have also for the text to work
 in general.


 Note that saving is not effected at all, both autosave and manually saving
 a problematic post works immediately with no appreciable problems or lags.


 When the timeouts happen they throw fatal errors for all kinds of
 different parts of the code in wp-includes/post.php, wp-includes/wp-db.php
 etc, including some line numbers that dont' exist (line 1237 of wp-db.php
 for example).

 They look like this:

 Fatal error: Maximum execution time of 30 seconds exceeded in /xxx/wp-
 includes/wp-db.php on line 169

 A given problematic title+content (like the one at
 http://pastie.caboo.se/189915 ) will consistently cause this to happen
 across several blogs I tested, but only if they were upgraded to 2.5.1.
 Sites that are 2.5.0 or less are totally fine and publish quickly like
 normal.

 I tried it on a fresh copy of 2.5.1 and it did not work. (this happens
 with no plugins installed and the title+content are enough to trigger it,
 I dont' think categories etc come into play). Slight variations on the
 text sometimes allow it through, though changing it to english always
 works.

 One thing that may be relevant is that switching the 2.5.0 files back in
 (which triggers an 'upgrade database' script of some kind and shows me the
 upgrade screen and afterwards shows the "you need to upgrade to 2.5.1"
 message) does NOT fix the problem, the blog must never have known 2.5.1 to
 be immune, which makes me think it might be one of the database changes
 (which I'm not that familiar with).

 Any leads about what might be causing it are appreciated. If someone could
 confirm that the text causes problems that would also be great. Thanks.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/6894>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software