Write all call frames of source location into trace Instead of only the top frame. Note this doesn't change how the stack trace itself is taken, this is simply using all the callframes that are already being taken. Drive-by change: take a sample when dispatching trace events for performance.measure calls. In DevTools, this give us more precise data when consolidating stack traces from samples and tracing. Bug: 381861194 Change-Id: I051fdb03b243af66ea449bf76cde3a665fc02a1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6063066 Commit-Queue: Andres Olivares <andoli@chromium.org> Reviewed-by: Michal Mocny <mmocny@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/main@{#1392357}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.