[wp-trac] Re: [WordPress Trac] #10236: Fatal error: Maximum execution time of 60 seconds exceeded in C:\xampp\_root_wordpress28_be\wp-includes\pomo\streams.php on line 26

[WordPress Trac]

#10236: Fatal error: Maximum execution time of 60 seconds exceeded in
C:\xampp\_root_wordpress28_be\wp-includes\pomo\streams.php on line 26
--------------------------+-------------------------------------------------
 Reporter:  codestyling   |       Owner:  nbachiyski                
     Type:  defect (bug)  |      Status:  new                       
 Priority:  high          |   Milestone:  2.8.1                     
Component:  i18n          |     Version:  2.8                       
 Severity:  blocker       |    Keywords:  crash re-created has-patch
--------------------------+-------------------------------------------------

Comment(by codestyling):

 I found also, this ''overload'' option contains additionally a bug inside
 PHP [http://bugs.php.net/bug.php?id=27421] and much more important, can be
 used to exploit or crash domains on the same server
 [http://www.securityspace.com/smysecure/catid.html?id=800373]

 This looks like dynamic runtime overload of other vhost's from neighbor
 vhost at same server using .htaccess file option.[[BR]]
 Sounds to me like more buggy code scenarios are inside because of
 difference between CLI and Apache run.

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