Add compatibility for the new profile format version with relevantForJS.#1450
Conversation
|
Unsetting review, I found some things that need to be cleaned up. |
Codecov Report
@@ Coverage Diff @@
## master #1450 +/- ##
==========================================
+ Coverage 80.61% 80.69% +0.08%
==========================================
Files 157 157
Lines 10748 10789 +41
Branches 2620 2623 +3
==========================================
+ Hits 8664 8706 +42
+ Misses 1885 1884 -1
Partials 199 199
Continue to review full report at Codecov.
|
70c061c to
cf8b08b
Compare
|
I'm not a big fan of this format, to be honest. We now have piles of repeated "false" values in every funcTable. Maybe a better format would be a |
| // Profiles now have a relevantForJS property in the frameTable. | ||
| // This column is false on C++ and JS frames, and true on label frames that | ||
| // are entry and exit points to JS. | ||
| const domCallRegex = /^(get |set )?\w+(\.\w+| constructor)$/; |
There was a problem hiding this comment.
It would be nice to provide a few examples of the types of names these match.
cf8b08b to
dac44af
Compare
Includes: - Add compatibility for the new profile format version with the relevantForJS column.
This PR contains the profile format changes for #1392 / bug 1500467 but does not have any user observable changes.