Andrés Olivares 435b3eb018 Make PerformanceModel processing async
In preparation to resolve function names in the perfomance panel using
source maps, this CL implements two functional changes:

1. The loadingComplete function of the PerformanceModel is set to be
   async. This is because the name resolving will require the result
   of async invocations and this function is ideal for adding the
   calls into (since this function commands the trace processing after
   all trace events are available). With this change, other functions in
   the call chain are updated accordingly (this includes calls in the
   legacy TimlineTestRunner)

2. To avoid race conditions, the PerformanceModel instance owned by the
   TimelinePanel is not used until the TimelineController has finished
   the processing pipeline. Before this CL, this waiting didn't happen
   made the code subject to race conditions, which were made evident
   with the implementation of (1).

Tests in Chromium land that make use of the updated helpers in the test
runner need to be updated before this CL can land.

Bug: 1364601
Change-Id: I2b7586337793eafd570e98947dcfbb574e6e43e5
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3941705
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
2022-10-17 12:34:13 +00:00
2022-05-30 08:50:17 +00:00
2022-10-17 10:08:13 +00:00
2022-10-17 10:08:13 +00:00
2022-07-13 09:26:00 +00:00
2022-07-13 09:26:00 +00:00
2022-01-19 12:53:26 +00:00
2021-04-16 07:38:35 +00:00
2020-08-21 05:51:47 +00:00
2020-05-29 14:29:42 +00:00
2022-09-19 08:56:09 +00:00
2022-01-17 12:49:00 +00:00
2022-10-17 04:16:12 +00:00
2022-07-15 09:09:49 +00:00
2021-11-17 16:23:44 +00:00

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

Source mirrors

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.

Getting in touch

S
Description
No description provided
Readme BSD-3-Clause
1.1 GiB
Languages
TypeScript 88.2%
JavaScript 5.7%
CSS 3%
HTML 1.4%
Python 0.8%
Other 0.8%