Manifest v3 High CPU Usages

[daniel k]

When I send message (from contents script to background),
"browser" CPU usages is over 100% from Chrome task manager (not window task manager)
extension CPU is okay but "browser" goes high


Bellow code is what i tested
https://github.com/ttop32/testChromeMessage
```
document.addEventListener("visibilitychange", function() {
  if (document.visibilityState === "hidden") {
    for (let i = 0; i < 1000; i++) {
        sendMessage();
    }                                                                                  
  }
});


function sendMessage() {
  chrome.runtime.sendMessage({
      type: 'message'
    },
    function(data) {}
  );
}
```


Add extension and refresh site few times makes High CPU Usages
It goes back when turn off extension



In my thought, send message then close makes ruined task

[wOxxOm]

Confirming the problem and also confirming there's no such problem in MV2 if I edit manifest.json:

  "manifest_version": 2,
  "background": {"scripts": ["background.js"]}

Might be related to https://crbug.com/1231683 but you should probably open a new bug report and don't forget to mention there's no problem in MV2 + background script.

This is yet another evidence that MV3 is nowhere near being stable even now, and it was a barely functional prototype when it was officially considered stable in Chrome 88 a year ago. This is the first time I closely observe a big corporation blatantly lying to everyone and still getting away with it.

[Jorge Dardon]

I'm aware that manifest V2 is going to be nuked in about a year, so our only option is V3.

As much as nobody really wants this change.

Is it really a mess in general, or more so in edge cases? 

[Cuyler Stuwe]

It’s a mess.

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/0ad7e142-976a-4357-97cd-46e8b187473an%40chromium.org.

[hrg...@gmail.com]

Is it really a mess in general, or more so in edge cases? 

Many bugs and missing features makes MV3 unusable at the moment.

The bad news is that it seems unlikely that all those bugs and missing features are solved during this year. The Extensions Team is moving too slow.

In all likelyhood, we'll be forced to migrate to a broken platform as the end of this year approaches.

 

[Jorge Dardon]

silly me for planning a software service for months and having an irreplaceable core usage be a chrome extension then.

[Cuyler Stuwe]

At least you haven’t built your entire career around specializing in Chrome extensions! 😅

--

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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/2034eace-9112-47d3-914e-da322d92f380n%40chromium.org.

[Simeon Vincent]

FYI, issue 1189678 has been resolved and merged into the M99 release branch. 

Simeon - @dotproto

Chrome Extensions DevRel

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CA%2BYuxdcA9bZmnXSMOTEVvc3Honq1SP6MgF0_70wPB-fmGBs1DA%40mail.gmail.com.

[Cuyler Stuwe]

Is that issue related to this CPU issue at all…? 🤔

[Simeon Vincent]

Whoops, wrong issue. Meant to link to https://crbug.com/1231683. Sorry about that!

Simeon - @dotproto

Chrome Extensions DevRel