I found an earlier discussion: https://groups.google.com/d/topic/google-chrome-developer-tools/OFUcgeZLH7M/discussion.
Adding the very first breakpoint takes unbelievably long. Te execusiont slows the more the more breakpoints you add. Removing all breakpoints and starting again doesn't help. Reloading the page doesn't help. If you close the browser tab and open a new one to debug your page it will run quicker again but the delay when putting the first breakpoint is still there... Running at 25.0.1364.172 m. --- Ferda On Thursday, June 7, 2012 1:18:17 PM UTC+2, Martin wrote: > > Hello, > > the following applies to both Chrome 19.0.1084.52 m using the > Developer Tools and Node.js 0.7.6 pre using node-inspector as Debug > Frontend. > I've noticed that setting a breakpoint (in frequently executed code), > no matter if the breakpoint is conditional or not slows down the > execution of javascript significally. > The function i'm trying to debug takes around 2 seconds to execute > without breakpoints. > If i set a breakpoint i stopped waiting for the end of execution (or > actually hitting the breakpoint) after 10 minutes! > Is this a known issue? > I haven't found anything related in the issue tracker. > > kind regards > Martin -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
