You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
AR: Debugger switches to line "/* we need a miracle */"
More generally, it scrolls current script to the very end, as it tries to go to line 3857049061
ER: Debugger should swith to line with "if" or to line with closing bracket of current function
Note:
It's not clear what component it is. Is it possible that JS engine reports something wrong that
confuses debugger? Or probably debugger itself should be updated to handle this properly.
I can't possibly know, because I don't do the development.
This is regression from bug 1261826. Regression range:
jasonLaster
changed the title
Debugger occasionally switches to line with large number when I step out of specific function
[Stepping] Debugger occasionally switches to line with large number when I step out of specific function
Jan 10, 2018
codehag
changed the title
[Stepping] Debugger occasionally switches to line with large number when I step out of specific function
[stepping] Debugger occasionally switches to line with large number
Jan 10, 2018
lukaszsobek
changed the title
[stepping] Debugger occasionally switches to line with large number
[Stepping] Debugger occasionally switches to line with large number
Jan 12, 2018
Bugzilla related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1326834
Todo: confirm if this is still happening
STR_1:
AR: Debugger switches to line "/* we need a miracle */"
More generally, it scrolls current script to the very end, as it tries to go to line 3857049061
ER: Debugger should swith to line with "if" or to line with closing bracket of current function
Note:
It's not clear what component it is. Is it possible that JS engine reports something wrong that
confuses debugger? Or probably debugger itself should be updated to handle this properly.
I can't possibly know, because I don't do the development.
This is regression from bug 1261826. Regression range:
The text was updated successfully, but these errors were encountered: