Web Console sometimes doesn't link to debugger
Categories
(DevTools :: Console, defect, P3)
Tracking
(Not tracked)
People
(Reporter: steely.wing, Unassigned)
Details
Attachments
(1 file)
|
18.29 KB,
image/png
|
Details |
Untitled.png
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131
Steps to reproduce:
- Open a test.html
```
<html>
<body>
<script>
console.log('test');
</script>
</body>
</html>
```
- Open web console, click the log message source link
- If the link go to debugger, re-open web console (press F12 twice)
- Click the source link again, it will link to view-source
- If I refresh the page, click the link again, it will link to debugger
In some web page, it always link to view-source even I refresh.
Actual results:
Source link link to view-source
Expected results:
Source link should link to debugger
|
Reporter | |
Updated•7 years ago
|
|
|
Reporter | |
Updated•7 years ago
|
|
||
Updated•7 years ago
|
|
||
Updated•6 years ago
|
|
||
Comment 1•5 years ago
|
||
Simpler STR:
- Go to
data:text/html,<meta charset=utf8><script>console.log("hello")</script> - Open the console
- Close devtools
- Re-open the console
- Click on the location of the
hellolog
-> Opens view:source
For some reason I can't understand, this doesn't reproduce every time 🤔
What I observe when this happens is that frame.sourceId is null when calling this.toolbox.viewSourceInDebugger.
cc Brian as he did some work on this area lately.
|
||
Comment 2•5 years ago
|
||
The problem here is that the source which called console.log() can be garbage collected before the debugger is opened, which prevents the server from being able to create a SourceActor which can be opened in the debugger. This is a similar issue to bug 1503422, though in this case the server can more easily detect that the relevant source has been GC'ed, because there is an ID on the console message information which does not correspond with any source which the debugger can find.
|
||
Comment 3•4 years ago
|
||
I think this should be fixed with https://bugzilla.mozilla.org/show_bug.cgi?id=1572596
Description
•