Profiling and benchmarking in MV3

[Matt]

Just wondering is there any update on how to debug performance issues?

[Patrick Kettner]

Hey Matt!

Generally speaking, profiling extension issues is the same as profiling web development issues. So standard performance docs apply. If you have a specific area of concern, would be more than happy to go into more detail, though!

patrick

On Fri, Nov 1, 2024 at 11:08 AM Matt <matthew...@gmail.com> wrote:

Just wondering is there any update on how to debug performance issues?

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/3dcff977-c985-4a30-9161-793fbdfae20cn%40chromium.org.

[woxxom]

Nothing's changed: performance-profiling of the background script is still broken in ManifestV3 and as you can see it's not even well-known. The workaround is to open another page of your extension or chrome-extension://id/manifest.json where id is the extension's id, duplicate this tab, open devtools in both tabs, in the first devtools go to Performance->start recording, in the second devtools go to Application->Service worker->click the "stop" link if it's shown, then click the "start" link.

[woxxom]

...note that you only need the second tab to profile the startup phase, otherwise just open one tab and start recording, then interact with the extension, and stop recording.

[Matt]

Thanks woxxom, I knew there was something not quite right with it as I'd read about it after trying to see if I could profile, the instructions I read were not as good as yours.

As a quick fix, can't the docs be updated to explain this for now?