Skip to content

[Feedback] Enhanced Traces experiment #122

Open
@captainbrosset

Description

@captainbrosset

tl;dr: Enhanced Traces is a new experimental feature coming with Microsoft Edge 109 which we'd love your feedback about.


Context

The Performance and Memory tools record runtime data about your webpage. Exploring the recorded data makes it possible to improve your webpage's memory usage or runtime performance. Additionally, the recorded data can be exported to files on disk. The exported files are called traces.

Exporting performance and memory traces is useful when you want to share these files with other people to get help with investigating issues. An exported trace is a .json, .heapsnapshot, .heapprofile, or .heaptimeline file. An exported trace file can be imported in DevTools at any time. By default, traces contain minimal information about the runtime data from the traced webpage.

Starting with Microsoft Edge 109, traces can experimentally be exported in a new enhanced format.

What's an enhanced trace

An enhanced trace is a .devtools file that contains more runtime data from the traced webpage. Enhanced traces make it much easier to resolve performance and memory issues by recreating the environment in which the trace was recorded and by providing original source files. An enhanced trace contains the execution context and the list of parsed scripts, and can optionally contain console messages, script sources, and a snapshot of the DOM tree.

When an enhanced trace is imported in DevTools, a new DevTools window appears. This new window isn't connected to the webpage that's running in your browser, and instead re-creates the environment in which the trace was originally recorded.

For example, if a snapshot of the DOM was recorded in the enhanced trace, the Elements tool displays this snapshot. If console messages were recorded, the Console tool prints these messages. The Sources tool displays the scripts that were present during the recording.

Using enhanced traces makes it possible to reliably resolve source code references found in imported traces to the actual runtime code in the Sources tool. Additionally, if source maps were presents when a trace was recorded, it will also be possible to resolve code references to their original source code.

Feedback

We're actively experimenting with this new feature.

If you've used enhanced traces and have any feedback to share with us, please feel free to leave a comment here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feedbackFeedback about an existing DevTools feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions