[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):

 Replying to [comment:5 nbachiyski]:
 > Replying to [comment:4 codestyling]:
 > > It requires to reboot Apache Server after changing this setting.
 > > Without a reboot the ''php.ini'' is cached and Apache doesn't notice
 this change.
 >
 > I reoot apache on every change of php.ini. The problem isn't with
 apache. It works (fails) as expected. The interesting thing is that in the
 CLI it never fails. I am sure the overload option is set to 2, there.
 This sounds interesting and should also be inverstigated. Maybe the CLI
 takes a different ''php.ini'' than Server (different environment path
 lookup) ?
 I think, the unit test may also require a "live" testing mode using a real
 servered page by Apache.

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