Hi Beau, thank for your suggestion, but I have already changed that parameter, but for other reason. The scope of that parameter is to avoid any script to block the whole browser (due to excessive resource usage, and thus extended execution time); my current problem instead is in stack depth, and I don't know how I could correlate it with execution time.
Regards, Giulio Cesare On 7/5/06, Beau Hartshorne <[EMAIL PROTECTED]> wrote: > > On 4-Jul-06, at 4:44 PM, Bob Ippolito wrote: > > > You definitely could if you recompiled Firefox, but the best way to > > track this down is to just use alerts or logging until you find it. > > In this situation, I agree with Bob and think alert/log is your best > bet. That said, try Firefox's about:config prefs, and look for > dom.max_script_run_time, and try playing with that value. The default > is '5' (seconds, my guess). > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
