Last modified: 2014-09-07 20:20:28 UTC
Possibly due to some difference in system load at different time, script execution time of the same page may differ. If the running time is close to the limit, it still works fine most of the time, but fails with a "Script error" randomly. When users report such a "Script error" or any consequence (eg. unexpanded template, missing *links etc.), it's difficult for us to diagnose until we get that "Script error" ourselves or have a look at the page source to find out that 9.x seconds execution time. It would be great to give a warning (or put pages in a category) if the running time exceeds a soft limit, and kill execution only when it exceeds the hard limit.
I'm now suspecting this causes bug 60147.