[Sources]: Bug fix where frontend is imporoperly handling a pausedEvent with empty callframes
Issue:
- the DevTools crashes when trying to access "callFrame.script" on line 472 of DebuggerWorkspaceBinding.js
- This is caused when there is no callframes in the callframes array
- The DevTools should handle this scenario gracefully without crashing
Changes:
- returning false early in _beforePaused
- This causes a "stepOver"/"stepInto" call and try to set the paused details at the new location
Bug: 1129220
Change-Id: I7d73aa9ff2b83298163e11516ec67450554ea39d
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2415235
Reviewed-by: Tony Ross <tross@microsoft.com>
Reviewed-by: Jack Lynch <jalyn@microsoft.com>
Commit-Queue: Michael Liao <michael.liao@microsoft.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found here.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools