Profile processing only works properly in Firefox

Open mstange opened this issue 5 months ago • 0 comments

new URL("moz-extension://08fb0bab-91a5-43dd-8872-fddac8b38dea/").origin is null in non-Firefox browsers.

If you use await Services.profiler.dumpProfileToFileAsync(...) in Firefox, and then load the file into profiler.firefox.com running in Chrome, then profile processing creates an incorrect resourceTable, mapping all add-on functions to the first extension.

Example: https://share.firefox.dev/4fj4bT0 (shows "Okta Browser Plugin", should be showing "1Password – Password Manager")

┆Issue is synchronized with this Jira Task

Jul 29 '25 19:07 mstange