Chrome 149-151 still crashes for me when I reload the extension if devtools for the service worker open on its Application tab

[woxxom]

https://crbug.com/466134219 claims to have fixed the crash but I still see it here. I commented in the bug report but 9 days and there's still no response.

I wonder why this is isn't a priority given that MV3 has severely degraded developer experience when debugging a complicated background script by breaking HMR (hot module reloading) as well as a simple Ctrl-R or F5 key in the background script devtools. How can we telegraph he importance of these use cases and break through the cognitive event horizon of the Chromium extensions team?

Without these features MV3 feels half-baked at best compared to a decade of almost perfect debugging experience in MV2 for the background script. To add insult to the injury, the fix for SW bugs a few years ago disabled the ability to forcefully update the service worker from another extension's page so the only way now is to reload the entire extension which is disruptive by itself due to the need to reopen the tabs and restore the state (unless you use a framework that deals with that) and if this isn't enough imagine dealing with Chrome crashing if you left devtools open on the Application tab.

[Oliver Dunk]

Hi woxxom,

Thanks for flagging this. I hadn't seen your comment but I am taking a look at the issue now.

I appreciate your frustration, and we can always do more, but I do want to point out that we closed this issue specifically as part of trying to improve the developer experience. Previously we had to disable inspecting IndexedDB from service workers because of the crash and the work here was part of making sure to bring that back.

It looks like we're not quite there yet, but we're trying :)

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

--
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/d29f52b7-a86b-49d0-ae4e-0395623df92cn%40chromium.org.