[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
--------------------------+-------------------------------------------------

Comment(by codestyling):

 Replying to [comment:1 Denis-de-Bernardy]:
 > see #10165
 I have tested this suggested replacement a bit, here are some intermediate
 results:[[BR]]

 1.) memory consume[[BR]]
 the current implementation utilizes 3.83MB on Windows machines[[BR]]
 the suggested replacement utilizes 2.54MB on Windows machines[[BR]]
 both values are average about 100 runs each.[[BR]]

 2.) the speed[[BR]]
 not yet tested and measured but ''feels'' to be a bit faster.[[BR]]

 3.) the compatibility[[BR]]
 It seems to work only with the main *.mo file from WordPress itself if
 replacement put on 2.8 version. All translatable plugins working with
 current file remain untranslated with new one class.[[BR]]

 Could be a base for a fix but not fully suitable as an adhoc replacement.
 And uses only PHP 5 construction and also ''protected'' / ''public'' /
 ''private'' modifier not available at PHP 4.[[BR]]

 4.) crash test[[BR]]
 It doesn't crash (fatal error) but it also doesn't show a translation.
 Also the WP main translation has been skipped in ''overload'' case. [[BR]]

 '''Conclusion'''[[BR]]
 The file may be a suggestion for what can be changed to preserve memory
 and also speed but nevertheless the ''overload'' also affects the str*
 functions of this suggestion and won't solve the issue!

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