Skip to content

Commit dbef9f2

Browse files
committed
Clarify that 'anatomy of a profile' doesn't describe object format
1 parent 13127f0 commit dbef9f2

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

  • files/en-us/web/api/js_self-profiling_api/profile_content_and_format

files/en-us/web/api/js_self-profiling_api/profile_content_and_format/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ In the first section we'll describe the [logical structure of a profile](#anatom
1212

1313
## Anatomy of a profile
1414

15+
In this section we'll describe the logical structure of a profile. Note that this isn't the same as the format of the object returned by returned by {{domxref("Profiler.stop()")}}: we'll describe that format in the next section of this guide.
16+
1517
A profile consists of an array of samples. Each sample consists of a timestamp and a call stack. Each call stack consists of an array of stack frames, and each stack frame contains information about the location of its corresponding function in the program:
1618

1719
![Diagram of a profile](profile.svg)

0 commit comments

Comments
 (0)