Guard against null event.data from worker in the script formatter The FormatterWorkerPool._onWorkerMessage method can call its current task's callback with null as its parameter. This happen when the formatter work doesn't send event data back. When this happens, it creates exceptions in the ScriptFormatter class. So, this change simply guards against this. Bug: 1132284 Change-Id: I9a995a2b81b5e211ae1690caad7bf56a4772c354 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2431404 Reviewed-by: Jose Leal <joselea@microsoft.com> Reviewed-by: Mathias Bynens <mathias@chromium.org> Commit-Queue: Patrick Brosset <patrick.brosset@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