[wp-trac] Re: [WordPress Trac] #5599: Sporadic timeout /wp-includes/gettext.php

WordPress Trac wp-trac at lists.automattic.com
Wed Jun 25 15:59:33 GMT 2008

#5599: Sporadic timeout /wp-includes/gettext.php
 Reporter:  WhitewolfFox              |        Owner:  westi   
     Type:  defect                    |       Status:  assigned
 Priority:  highest omg bbq           |    Milestone:  2.6     
Component:  General                   |      Version:  2.3.2   
 Severity:  critical                  |   Resolution:          
 Keywords:  gettext unpack() timeout  |  
Comment (by codestyling):

 Replying to [comment:15 Jnet]:
 > I got similar problems for several of my clients using a .mo-file. I
 tried the fix suggested by
 [http://trac.wordpress.org/ticket/5599#comment:14 codestyling] and
 [http://trac.wordpress.org/ticket/3780#comment:23 #3780], both without

 What does similar meen?
 Did you get unpack() errors anyway or only max runtime exceeded ?

 btw: This kind of issue have been tracked down over several blogs and i
 found similarities:
  - seems to require Apache 2.x Server (1.x not affected)
  - seems to require PHP 5 Version (PHP 4 not affected)
  - seems to require mod_php (no occurance at cgi versions)
  - seems to require 64Bit Architecture (even if running 32Bit Unix/Linux)
  - seems to require dedicated hoster (massively occured at hoster all-
  - seems to require more traffic as normal to happen

 The tested system affected is hosted at all-inkl.com and runs at
  - Linux dd10606 SMP Tue Apr 15 18:13:27 CEST 2008 i686
  - PHP 5.2.5
  - Apache APi Version: 20051115
  - PHP API 20041225
  - PHP Extension 20060613
  - Zend Extension 220060519
  - protected with the Suhosin Patch
  - additional modules: ionCube Loader / sysvsem / sysvshm
 At this server the patch above does work, but it's not the full solution
 i'm afraid.
 It's not clear, why sporadically this substr() bug occures. Mostly this
 server runs well and uses correct the *.mo-files but under pressure it
 happens but very seldom.
 I also read reports, that server may fails at every attempt to read any
 *.mo-file, so they have only the chance to disable usage and fall back to
 I assume, that this could also be related to SMP system (multi core's)
 that are not qualified supported at PHP ?

Ticket URL: <http://trac.wordpress.org/ticket/5599#comment:16>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list