chromium debugger teleports my breakpoints

SDK/Debugger version:
Eclipse version:
Google Chrome/V8 Embedder + version:
[For WebKit (WIP) protocol] Backend version:
OS + version:

What steps will reproduce the problem?
(see attached screenshots)
I can't find an out-of-the-box use case, but it happenned often to me.
Here I have an exception thrown at line 192. So I'm adding a breakpoint 
here(see picture#1), and then hit F5 to refresh and see what's going on. But 
when the page refresh, the debugger would mysteriously "teleport" the 
breakpoint to another line (here, to line 456, see picture#2).

What is the expected result?
just let this damned breakpoint where it should be

What happens instead?
the breakpoint is moved somewhere else (here, about 200 lines below ...)

Please provide any additional information below. If possible, attach a
(reduced) test-case.
once the page had been refreshed and the breakpoint moved, I can't add the 
breakpoint anymore, like shown in picture#3. (at this point, the debugger is 
paused at the moved breakpoint, ie l.456).

now i've wipped the cache and rebooted chrome. The breakpoint is still warped 
the first time, but at the next refresh can readd the breakpoint to line 192 
correctly, unlike describe in the paragraph just below.

Original issue reported on code.google.com by rg1...@gmail.com on 11 Jan 2013 at 3:25

Attachments:

cczw2010 / chromedevtools

chromium debugger teleports my breakpoints #82