(In reply to Daniel Holbert [:dholbert] from comment #6) > (In reply to alex_mayorga from comment #5) > > I captured another profile FWIW: > > Would you mind recording another profile? That one from comment 5 seems to have failed to get symbols for some reason, which makes it hard to interpret. (Its backtrace show a lot of things like `0x7ff9ffa85799 xul.dll` instead of the function name.) (I think this can happen randomly sometimes, if e.g. there's a network error communicating with the web-hosted symbols server just after you capture the profile.) Symbolication errors are now easily recoverable without needing to re-capture a profile. In the profiler UI, you can click on the "Profile Info" button to open the profile meta data panel. There you can click a "Re-symbolicate profile" button. I re-symbolicated and re-uploaded for you the profile from comment 6: https://share.firefox.dev/3eoGoDl
Bug 1698855 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Daniel Holbert [:dholbert] from comment #6) > (In reply to alex_mayorga from comment #5) > > I captured another profile FWIW: > > Would you mind recording another profile? That one from comment 5 seems to have failed to get symbols for some reason, which makes it hard to interpret. (Its backtrace show a lot of things like `0x7ff9ffa85799 xul.dll` instead of the function name.) (I think this can happen randomly sometimes, if e.g. there's a network error communicating with the web-hosted symbols server just after you capture the profile.) Symbolication errors are now easily recoverable without needing to re-capture a profile. In the profiler UI, you can click on the "Profile Info" button to open the profile meta data panel. There you can click a "Re-symbolicate profile" button. I re-symbolicated and re-uploaded for you the profile from comment 5: https://share.firefox.dev/3eoGoDl