This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 146789 [details] Netbeans project reproducing the bug To reproduce, open the attached project and set a breakpoint in hello.js on line 8 (inside the constructor). Run the project with Chrome connector. The breakpoint is moved (and hit) on the prototype definition. I debugged it and I think it might be due to this chrome bug: https://code.google.com/p/v8/issues/detail?id=2825 I suspect this is this bug because the chrome's "Debugger.breakpointResolved" event for my breakpointId "http://localhost:8383/html5-sandbox/hello.js:7:0" have for location: location: { columnNumber: 5 lineNumber: 12 scriptId: "24" } (Note how line number became 12 instead of 7). I also attached a patch for netbeans because the plugin path seems out of date.
Created attachment 146790 [details] Fix chrome plugin path
Reproducible. As for the patch file, this is not related to this issue. Could you please file a new issue to web/html project and describe what's wrong and why the patch is needed? Adding Tomas to cc as owner of web/html project Thank you.
Here it is: https://netbeans.org/bugzilla/show_bug.cgi?id=243920
As suggested here: https://code.google.com/p/v8/issues/detail?id=2825 starting chromium via: $ chromium --js-flags="--nolazy" fixes the problem. So that confirms that it is a chrome bug and gives a workaround. Do we want to integrate it in netbeans knowing that if chrome/chromium is already started it will have no effect?