Update to DevTools enhanced traces documentation #3615
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
microsoft-edge/devtools/performance/share-performance-traces.md
Outdated
Show resolved
Hide resolved
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Oct 23, 2025
mikehoffms
reviewed
Nov 4, 2025
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 2b77065: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
|
Learn Build status updates of commit bc133b4: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit cba66ef: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 26575e6: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
mikehoffms
reviewed
Nov 6, 2025
microsoft-edge/devtools/performance/share-performance-traces.md
Outdated
Show resolved
Hide resolved
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 9baaaef: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
mikehoffms
reviewed
Nov 6, 2025
| * **Include script sources in .devtools traces**. | ||
| * **Include DOM snapshots in .devtools traces (experimental)**. | ||
|
|
||
| <!-- todo: create png & un-comment after new ui is in canary: --> |
Collaborator
There was a problem hiding this comment.
create enhanced-trace-options.png, after new ui is in canary
shows the Settings panel in DevTools, showing the trace options
mikehoffms
reviewed
Nov 6, 2025
|
|
||
| 1. When the snapshot is recorded, click the **Save** button in the **Memory** tool sidebar: | ||
|
|
||
| <!-- todo: create png & un-comment after new ui is in canary: --> |
Collaborator
There was a problem hiding this comment.
create exporting-memory-trace.png, after new ui is in canary
shows Edge w/ DevTools, showing the Memory tool, with the Save button
mikehoffms
reviewed
Nov 6, 2025
|
|
||
| 1. Choose the trace type and a location to save the trace file on your disk. Select `.devtools` if you want to include console messages, script sources, and DOM elements. Otherwise, select `.heapsnapshot`, `.heapprofile`, or `.heaptimeline`. | ||
|
|
||
| <!-- todo: create png & un-comment after new ui is in canary: --> |
Collaborator
There was a problem hiding this comment.
create saving-memory-trace.png, after new ui is in canary
shows the Windows save dialog, showing the memory trace file being saved in a traces folder
mikehoffms
reviewed
Nov 6, 2025
| * [JavaScript debugging features](../javascript/reference.md) | ||
| * [Run snippets of JavaScript on any webpage](../javascript/snippets.md) | ||
|
|
||
| <!-- |
Collaborator
There was a problem hiding this comment.
update 404 link: [Save performance traces] ( https://developer.chrome.com/docs/performance/save-trace/ )
maybe copy valid link into article body
https://developer.chrome.com/s/results?q=Save%20performance%20trace
|
Learn Build status updates of commit 5e9b2f7: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
mikehoffms
reviewed
Nov 7, 2025
|
|
||
| 1. Select or clear the checkboxes, to control what information to include in the trace file: | ||
|
|
||
| * The **Include annotations** checkbox.<!-- tooltip: todo; none? --> |
Collaborator
There was a problem hiding this comment.
check latest UI in dialog, note the tooltips
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit add1b3e: ✅ Validation status: passed
This comment lists only the first 25 files in the pull request. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered article sections for review:
Share memory traces with more data
/devtools/experimental-features/share-memory-traces.mdShare enhanced performance and memory traces
/devtools/experimental-features/share-traces.mdShare performance traces with more data
/devtools/performance/share-performance-traces.mdBackground
Enhanced performance traces is shipped upstream. There is a new export UI, and it's no longer considered an experiment. The documentation for this file will live under the Performance section.
Enhanced memory traces remain only downstream. We will keep this documentation under the Experimental features section.
Also, we are no longer using the term "enhanced traces" publicly and it will only be used internally. We need to update our documentation to remove this term.
AB#59906695