Breakpoints not showing the highlight bar for current code line (Chromium 14.0.825 on Linux)

155 views
Skip to first unread message

Tim Meadowcroft

unread,
Jul 25, 2011, 8:55:37 PM7/25/11
to google-chrome-...@googlegroups.com

Sometime around this version (possibly a slightly earlier v14) then sometimes when the developer tools stop at a breakpoint, the correct script line is highlighted (blue bar in script window) but other times the "run/pause" button changes correctly and the call stack is populated but the "blue bar" doesn't show to indicate the current line. If I then select the top stack frame in the call stack display, the blue bar ALWAYS shows in the source window.

This happens not just for user breakpoints but also for "F10" style (step-over/step-into operations).
Now that I know of it, it's not too bad, just annoying, but first few times I thought the code was still running but I had some bad loop somewhere :)

I can't seem to find a pattern to reproduce it - sometimes it shows, other times not, but am happy to run tests if required.

By the way, loving the "full url of script files in the tooltip of the script file dropdown" feature - thanks for that !

--
T

PhistucK

unread,
Jul 26, 2011, 2:11:52 AM7/26/11
to google-chrome-...@googlegroups.com
I second that. Can you file an issue at new.crbug.com (if you do not find any existing one at crbug.com)?

Thank you.

PhistucK

Pavel Podivilov

unread,
Jul 26, 2011, 5:32:12 AM7/26/11
to google-chrome-...@googlegroups.com
Hi Tim,

What you describe looks very similar to this issue - https://bugs.webkit.org/show_bug.cgi?id=64995 (fixed few days ago). Could you please open inspector on inspector and check if you have any exceptions there?

BR,
Pavel Podivilov

Tim Meadowcroft

unread,
Jul 26, 2011, 6:50:37 AM7/26/11
to google-chrome-...@googlegroups.com

Sure thing - I was just hunting thru crbug.com to check for possible duplicates before making a new issue.

Will inspect it next time it bites and report back here (and log a crbug if it looks different)

--
T

Tim Meadowcroft

unread,
Jul 26, 2011, 8:55:13 AM7/26/11
to google-chrome-...@googlegroups.com

Yep, the inspector on inspector shows

   "Uncaught TypeError: Cannot read property 'sourceURL' of undefined    DevTools.js:48019"

which matches some of the details in the webkit report, so if you're happy it's the same issue (and is fixed upstream) then I won't bother with a crbug report

Cheers 

--
Tim

Pavel Podivilov

unread,
Jul 26, 2011, 10:53:18 AM7/26/11
to google-chrome-...@googlegroups.com
Yes, it's the same issue.

BR,
Pavel Podivilov
Reply all
Reply to author
Forward
0 new messages