Duplicate service workers with manifest v3

[Samala Kranthi]

I am facing this issue where duplicate service workers are created. During this stage post messages don't reach service worker at all. Does any one have any idea on why this happens and do we have a way to stop this. 

[Oliver Dunk]

Hi Samala,

We've definitely seen some reports of behaviour like this, but haven't been able to reproduce.

Is this something you are seeing rarely or are you able to share an extension where this happens fairly often?

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

On Tue, May 16, 2023 at 12:27 PM Samala Kranthi <mekran...@gmail.com> wrote:

I am facing this issue where duplicate service workers are created. During this stage post messages don't reach service worker at all. Does any one have any idea on why this happens and do we have a way to stop this. 

--
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/a3464ae5-5bde-48b4-b7eb-60097a1f9683n%40chromium.org.

[Samala Kranthi]

Hi Oliver,

This rarely happens and there are no systematic steps which can be followed in order to reproduce this issue. Is it possible to add some logging in our code for when two services workers are detected. 

And is it possible to do performance recording it seems to be completely disabled for extensions, this could help us debug some issues which face.

[Uladzimir Yankovich]

This bug is 1.5 years old. It remains only to pray. Most often, our users encounter it when updating the extension.

[Samala Kranthi]

Here it is.

[Oliver Dunk]

Thanks for the extra information, it's unfortunate that this isn't reproducible.

I don't think there's anything specific you can add in logging right now, but if you find a way to get in to this situation then please do let us know.

On our side there are a few stability bugs that we're keeping an eye on and trying to investigate, this one included. I'm really hopeful we can get to the bottom of them.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Jordi Salvat i Alabart]

What's the ticket in bugs.chromium.org? I've not been able to find it...

El dia dimecres, 17 de maig de 2023 a les 11:08:46 UTC+2, Oliver Dunk va escriure:

[Oliver Dunk]

I'm actually not seeing one for multiple service workers specifically - you could open a new one, but I'm slightly hesitant to do that since once we fix some of the other bugs we may find that it is the same problem. But not against it.

Here's an example of one of the more active ones that is definitely still on our minds: https://bugs.chromium.org/p/chromium/issues/detail?id=1271154

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Uladzimir Yankovich]

Yes, this is our ticket. When we created it, the error was reproduced stably and easily. But, unfortunately, at that moment we were the pioneers of V3 and no one wanted to pay attention to this problem.

--

Uladzimir Yankovich,

Founder @ Manganum (manganum.app).

[Don Schmitt]

We were experiencing this frequently in early December, but since we weren't able to find a reliable way to reproduce it we did not enter a bug  at crbug.com.  It seemed to go away later in December.  Not entirely sure if that was due to changes that we added or a Chromium update.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAFc1iR6Em8zeFOBmzpek3V5Fgb4Ab2Lg%3DMgMPUJb-7qfASdeqg%40mail.gmail.com.