After 2 minutes, it unloads itself #1974

thany · 2022-10-24T08:27:56Z

Vue devtools version

6.4.5

Link to minimal reproduction

N/A

Steps to reproduce & screenshots

Sorry, no reproduction. I don't know what causes the problem, so I have no way of knowing how to make a reproduction.

Go to a Vue2 website in Firefox
Open the devtools
Wait a few minutes
Maybe you have to do some random stuff in the devtools

What is expected?

Nothing happens. Devtools stays open, and stays functional.

What is actually happening?

One of two things may happen:

The devtools unloads itself, showing just its logo.
The devtools reloads itself, undoing any changes and closing the tree.

In either case, should I have been debugging, making changes, etc, I can just go and start all over. Any work that I'm doing in the devtools is rudely interrupted and goes poof, i.e. it doesn't remember any changes and doesn't recover them.

System Info

System:
    OS: Windows 10 10.0.19044
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 10.41 GB / 31.76 GB
  Binaries:
    Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 106.0.5249.119
    Edge: Spartan (44.19041.1266.0), Chromium (106.0.1370.52)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vue: ^2.6.14 => 2.6.14

I don't know why so many people use this script, it's poop. Firefox is not in there.

Any additional comments?

Worked fine in some older version. Don't know which one, since browser addons update fully automatically.

vue-bot · 2022-10-24T08:27:57Z

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

ThaDaVos · 2022-10-26T07:29:44Z

I am running into the same issue, but with Vue 3 apps instead - it seems the reconnection logic (I read about it somewhere) may be the cause - the thing is, it's really annoying as I cannot simply restart the extension - re-opening the browser devtools fixes it though

ThaDaVos · 2022-10-26T07:30:44Z

Hello, thank you for taking time filling this issue!

However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).

I hope to see your helper-created issue very soon!

Sadly they can't - as the Issue Helper is missing vue-devtools ;)

yi0n · 2022-10-26T07:37:50Z

I can confirm this on Linux with Firefox.

golgote · 2022-10-26T09:40:45Z

Same issue with Firefox Developer Edition v107.0b5 (64 bits) on OSX (Monterey but saw the same problem on BigSur) with vue 2.7.13 and devtools 6.4.5

Billybob · 2022-10-26T12:10:19Z

Confirm this on Arch Linux with Firefox

denisgruba · 2022-10-26T16:21:17Z

Same issue with Firefox Developer Edition v107.0b5 (64 bits) on OSX (Monterey but saw the same problem on BigSur) with vue 2.7.13 and devtools 6.4.5

+1 on the same config, except vue 2.6

dmke · 2022-10-27T12:21:44Z

I tried to debug this, by inspecting the extension while it un-/reloads. Navigating to about:debugging#/runtime/this-firefox → Extensions → Vue.js devtools → Inspect, and monitoring the console yielded the following warning message:

⚠️ Background event page was not terminated on idle because a DevTools toolbox is attached to the extension.

The extension itself then did not unload/reload.

I'm guessing Firefox tries to unload the background page (because it determined it was idle), which triggered a reload of the extension.

Not sure how to proceed from here, as I'm not experienced in extension authoring.

Edit, forgot to mention: Firefox 106.0.2, Vue.js devtools 6.4.5, Debian Linux stable/11.5

ThaDaVos · 2022-10-27T17:49:16Z

I noticed, as I am currently debugging performance issues, that if I disable all layers on the timeline tab - it will stay working for longer - but that may also be as I keep interacting with it longer (or the timeline page is more active)

Androphin · 2022-10-27T19:09:41Z

Isn't it possible to disable the time grid anymore?

thany · 2022-10-28T11:16:39Z

How is this being solved in the React devtools? I'm guessing the two must've been set up similarly, so perhaps the solution is quite similar as well.

thany · 2022-10-31T15:05:27Z

Can we please get some prioity behind this issue? It's still a problem and it's really annoying to have an invisible timer that counts down to the devtools unloading itself.

It's not possible to downgrade a browser addon. Due to the severety/impact of this bug, I propose someone does one of two things:

Publish an earlier version, like sort of right now.
Fix this bug within a reasonable amount of time, which sort of already expired, afaic.

Please let us know which it's going to be, dear devs.

Locheed · 2022-11-03T10:01:28Z

Yep. This really bugs me. I have to use Chrome when I need to use Vue devtools. Unusable with a FF. There was another ticket before this with same issue: #1950

Billybob · 2022-11-04T12:56:23Z

Seems to work!
Arch Linux, Firefox =106.0.3, Vue 2.6.14, devtools 6.4.5

lhapaipai · 2022-11-07T14:45:33Z

Unfortunately I still encounter the problem, with

Manjaro Linux
Firefox 107.0b6
Vue 3.2.37
devtools 6.4.5

impossible to work properly with such a problem. current solution
downgrade to firefox 105

pyrsmk · 2022-11-08T10:01:14Z

Same issue on MacOS.

matthewhutchings · 2022-11-08T10:16:54Z

also having this issue

craigrileyuk · 2022-11-08T13:32:34Z

Same: Firefox 106 on MacOS Ventura with devtools 6.4.5

cmauf · 2022-11-08T14:25:25Z

same here: Firefox 106.0.4 on Manjaro 5.15.76, Devtools 6.4.5

For me it's like 15 secs before the devtools die

pisandelli · 2022-11-08T14:51:50Z

Same here...
Linux Pop_OS
Firefox: 106.0.3 (64-bit)

Is very annoying... I need to reload the page every 15sec.

cyberlyght · 2022-11-09T19:20:33Z

Same problem. After a short amount of time the Vue devtools tab goes blank and only shows <\> Sometimes it comes back on. It seemed to start happening in October.
Windows 11 Pro 22H2
Firefox 106.0.5 (64-bit)
Vue.js devtools 6.4.5
Vue 2.6.12

Acartuerk · 2022-11-14T08:44:09Z

Can confirm this as well with:
Windows 10 Enterprise, 21H2
Firefox 106.0.5
Node 18.9.0.
Vue 3.2.41
Vue.js devtools 6.4.5

tylerFretz · 2022-11-14T19:36:03Z

Yep same problem.
Windows 11 Home
Firefox 106.0.5
Vue 2.6.14
Vue.js devtools 6.4.5

uclnj · 2022-11-15T12:50:16Z

Same issue now.
Firefox 106.05
Winblows 10 Pro
Vue 2.6.12
Devtools 6.4.5

To add, occasionally, Firefox freezes when hovering over components (highlighting in green in the browser) and the tab instance skyrockets to 4.1GB of RAM then suddenly drops to 300MB where it normally hovers. It is constantly loading/unloading to the point I've had to break down and use ... Edge, to debug development.

Edge..I've demeaned myself to using Edge to keep using Vue Devtools.

Update - still doing it after upgrading to FF 107 just now.

matt-smarsh · 2022-11-16T22:46:25Z

Same issue for me as well. After a period of time (30s to a minute) the Vue tab of Inspector reboots itself, and then another period after that it crashes and doesn't come back.

System:
  OS: Windows 10 10.0.19044
  CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
  Memory: 5.98 GB / 15.75 GB
Binaries:
  Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
  npm: 9.1.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Firefox: 107.0
npmPackages:
  vue: v2-latest => 2.7.10

matt-smarsh · 2022-11-16T22:53:55Z

From @dmke:

I tried to debug this, by inspecting the extension while it un-/reloads. Navigating to about:debugging#/runtime/this-firefox → Extensions → Vue.js devtools → Inspect, and monitoring the console yielded the following warning message:

⚠️ Background event page was not terminated on idle because a DevTools toolbox is attached to the extension.

The extension itself then did not unload/reload.

I'm guessing Firefox tries to unload the background page (because it determined it was idle), which triggered a reload of the extension.

Not sure how to proceed from here, as I'm not experienced in extension authoring.

Edit, forgot to mention: Firefox 106.0.2, Vue.js devtools 6.4.5, Debian Linux stable/11.5

I wonder if the problem is the background tab unloading, perhaps just changing this persistent key from false to true would fix that? What other side effects would be caused by changing this though? I've never made a Firefox extension to know though...

https://github.com/vuejs/devtools/blob/main/packages/shell-chrome/manifest.json#L31

dmke · 2022-11-17T08:42:31Z

I wonder if the problem is the background tab unloading, perhaps just changing this persistent key from false to true would fix that? What other side effects would be caused by changing this though? I've never made a Firefox extension to know though...

https://github.com/vuejs/devtools/blob/main/packages/shell-chrome/manifest.json#L31

MDN says to manifest.json#/background (emphasis mine):

The background key can also contain this optional property:

persistent - A Boolean value.

If omitted, this property default to true in Manifest V2 and false in Manifest V3. Setting to true in Manifest V3 results in an error.

Currently, Vue devtools has set "manifest_version": 2, but AFAIK even Mozilla deprecated it in favour of v3 (+ a set of extensions to keep ad blockers working). So even if setting "persistent": true is the solution, will only work for so long...

Charl13 · 2022-11-17T09:15:30Z

I also experience this issue (crashing and rebooting) of the Vue devtools.

Ubuntu 20.04.4 LTS
Firefox 106.0.2 (64-bits)
Vue devtools 6.4.5
Vue 3.2.41

But besides just crashing and rebooting in my case the Vue devtools slows down the application in an extend where it becomes unusable. When I switch to Chromium 107 it works without issues.

Like @Locheed mentioned in #1974 (comment) there is another (closed) issue where this problem is described. It also states this starts to occur in Firefox 106 because they changed the way Firefox handles extension background pages.

This led me to download Firefox Extended Support Release (ESR) where (for me) the problem doesn't occur.

This is not the solution but a work-around for those who experience this problem and need to deliver their stuff yesterday 😅

Note: The Linux variant is an compressed version of Firefox Extended Support Release (ESR) which doesn't require actual installation.

Note: Since Firefox's downgrade protection it creates a new profile by default. I was able to sync my profile by using the --allow-downgrade flag (as mentioned on the page) and logging in with my Firefox account.

thany · 2022-11-17T09:18:24Z

Please elevate priority for this bug.

Is anyone actually working on this? If not, please do. It's taking a long time, so if there's any additional information required, please do ask for it, don't wait around.

thatCodingNoob · 2022-11-17T10:15:29Z

Updated Firefox to 107.0 and it seems to fix it

denisgruba · 2022-11-21T10:47:56Z

Do we actually know the devs are aware of the problem? Very top response is a bot response that the message wasn't submitted properly. It's possible that they use an issue tracker instead of checking this page, and never been made aware of this problem outside of the closed issue #1950. Usually you get some fairly quick responses from the devs on other issues, might be the case this one went under the radar.

dmke · 2022-11-28T16:29:30Z

Good point. I've asked in their forums.

thany · 2022-11-29T10:28:55Z

Do we actually know the devs are aware of the problem? Very top response is a bot response that the message wasn't submitted properly. It's possible that they use an issue tracker instead of checking this page, and never been made aware of this problem outside of the closed issue #1950. Usually you get some fairly quick responses from the devs on other issues, might be the case this one went under the radar.

This issue is enough. If they aren't looking at any github issues, they are missing out on a whole bunch of other issues, surely. Plus it doesn't make sense to copy things over using some kind of half-working system to another issue tracker when you've already got a perfectly good one right here.

uclnj · 2022-11-29T21:00:29Z

After updating FF to 107.0.1 the debugger now shows this on the extension

Reading manifest: Warning processing version_name: An unexpected property was found in the WebExtension manifest.

Akryum · 2022-12-05T09:41:28Z

Firefox recently broke addons as they changed the behavior of background pages.
I guess this is a side-effect of it - it will probably be fixed when we switch the extension to Manifest v3.

dmke · 2022-12-05T09:52:06Z

@Akryum: Can you estimate how difficult the migration to Manifest v3 is?

Would it be possible to build an interim version, with background.persisted = true (as suggested here: #1974 (comment))? I'll offer myself as beta tester for that :)

Akryum · 2022-12-05T10:02:27Z

main...manifest-v3

dmke · 2022-12-05T10:34:53Z

I've followed this guide to test the FF addon: https://devtools.vuejs.org/guide/contributing.html#testing-as-firefox-addon, however the yarn run:firefox task fails with "Unsupported manifest version: 3":

Console output

$ web-ext --version
7.4.0

$ web-ext run -s packages/shell-chrome -a dist -i src --verbose
[$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js][info] Version: 7.4.0
[$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js][debug] Discovering config files. Set --no-config-discovery to disable
[$HOME/.config/yarn/global/node_modules/web-ext/lib/config.js][debug] Discovered config "$HOME/.web-ext-config.js" does not exist or is not readable
[$HOME/.config/yarn/global/node_modules/web-ext/lib/config.js][debug] Discovered config "$HOME/code/github.com/vuejs/devtools/web-ext-config.js" does not exist or is not readable
[$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js][info] Applying config file: ./package.json
[$HOME/.config/yarn/global/node_modules/web-ext/lib/config.js][debug] Loading JS config file: "$HOME/code/github.com/vuejs/devtools/package.json" (resolved to "$HOME/code/github.com/vuejs/devtools/package.json")
[$HOME/.config/yarn/global/node_modules/web-ext/lib/config.js][debug] Looking for webExt key inside package.json file
[$HOME/.config/yarn/global/node_modules/web-ext/lib/config.js][debug] Config file $HOME/code/github.com/vuejs/devtools/package.json did not define any options. Did you set module.exports = {...}?
[$HOME/.config/yarn/global/node_modules/web-ext/lib/cmd/run.js][info] Running web extension from $HOME/code/github.com/vuejs/devtools/packages/shell-chrome
[$HOME/.config/yarn/global/node_modules/web-ext/lib/util/manifest.js][debug] Validating manifest at $HOME/code/github.com/vuejs/devtools/packages/shell-chrome/manifest.json
[$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/firefox-desktop.js][debug] Creating new Firefox profile
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/index.js][debug] Running Firefox with profile at /tmp/firefox-profileWpFkkf/
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/index.js][debug] Executing Firefox binary: /usr/bin/firefox
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/index.js][debug] Firefox args: -start-debugger-server 46777 -foreground -no-remote -profile /tmp/firefox-profileWpFkkf/
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/index.js][info] Use --verbose or --devtools to see logging
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to the remote Firefox debugger
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (0); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (1); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (2); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (3); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (4); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/index.js][debug] Firefox stdout: Started devtools server on 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Retrying Firefox (5); connection error: Error: connect ECONNREFUSED 127.0.0.1:46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connecting to Firefox on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js][debug] Connected to the remote Firefox debugger on port 46777
[$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js][error] 
WebExtError: installTemporaryAddon: Error: Error: Could not install add-on at '$HOME/code/github.com/vuejs/devtools/packages/shell-chrome': Error: Unsupported manifest version: 3
    at RemoteFirefox.installTemporaryAddon (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js:90:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async FirefoxDesktopExtensionRunner.startFirefoxInstance (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/firefox-desktop.js:218:27)
    at async FirefoxDesktopExtensionRunner.run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/firefox-desktop.js:51:5)
    at async Promise.all (index 0)
    at async MultiExtensionRunner.run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/index.js:68:5)
    at async run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/cmd/run.js:178:3)
    at async Program.execute (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js:263:7)
    at async file://$HOME/.config/yarn/global/node_modules/web-ext/bin/web-ext.js:13:1

[$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js][debug] Command executed: run

$ echo $?
1

How to proceed from here?

Akryum · 2022-12-05T11:08:27Z

Did you turn MV3 on in FF?
https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/

dmke · 2022-12-05T11:18:01Z

No, but even with both config toggles active, I still get "Unsupported manifest version: 3". When starting web-ext with --firefox-preview, I get another error ("background.service_worker is currently disabled"):

Console output

$ web-ext run -s packages/shell-chrome -a dist -i src --firefox-preview

Applying config file: ./package.json
Running web extension from $HOME/code/github.com/vuejs/devtools/packages/shell-chrome
Configuring Firefox preferences for Manifest V3
Setting custom Firefox preferences: {
  "extensions.manifestV3.enabled": true
}
Use --verbose or --devtools to see logging

WebExtError: installTemporaryAddon: Error: Error: Could not install add-on at '$HOME/code/github.com/vuejs/devtools/packages/shell-chrome': Error: background.service_worker is currently disabled
    at RemoteFirefox.installTemporaryAddon (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/firefox/remote.js:90:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async FirefoxDesktopExtensionRunner.startFirefoxInstance (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/firefox-desktop.js:218:27)
    at async FirefoxDesktopExtensionRunner.run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/firefox-desktop.js:51:5)
    at async Promise.all (index 0)
    at async MultiExtensionRunner.run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/extension-runners/index.js:68:5)
    at async run (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/cmd/run.js:178:3)
    at async Program.execute (file://$HOME/.config/yarn/global/node_modules/web-ext/lib/program.js:263:7)
    at async file://$HOME/.config/yarn/global/node_modules/web-ext/bin/web-ext.js:13:1

In about:config, I see devtools.serviceWorkers.testing.enabled = true, and dom.serviceWorkers.enabled = true, but no background.service_worker key.

This is with FF 107.0.1. Do I need the Nightly or Developer edition for this?

dmke · 2022-12-05T12:32:32Z

In FF 108.0b9 (Developer Edition), I get the same error.

It seems, background.service_worker refers to the entry in manifest.json, which is not yet supported by Firefox (see compat chart). This blog post from 2022/10/31 reads a bit like Mozilla prioritizing "Event Pages" over background service workers.

Btw. I've changed background.persisted to true in the main-branch manifest.json, and the unloading does not occur. I'll prepare a PR.

Firefox starting with version 106 introduced a change which apparently broke background pages. For the Vuejs devtools, this surfaced as extension unloading when the browser reached an "idle" state. User having the extension open noticed it as a unloading/reloading of the devtools tab. By setting background.persisted to true in the manifest.json, the unloading stopped. Note: This is a temporary solution, until Manifest v3 is properly supported.

dmke · 2022-12-05T12:42:44Z

#2000 will fix this issue.

djpowers · 2022-12-15T22:46:43Z

Thanks @dmke for investigating and coming up with a fix!

I've been experiencing this issue for a while now so I'm looking forward to it being resolved. Is there anything else that needs to be done to have this merged and released?

dmke · 2022-12-16T08:22:21Z

Is there anything else that needs to be done to have this merged and released?

It'd be nice if someone would test #2000 against a Chromium-based browser, just to see that it doesn't break anything: https://devtools.vuejs.org/guide/contributing.html#testing-as-chrome-addon

dmke · 2022-12-22T12:07:35Z

I've found a VM where I dared to install Chrome into. As far as I can tell, the extension does not break, but displays a warning regarding Manifest v2 being deprecated (as expected).

For the impatient and trusting, I've build a .xip including this fix:

6.4.5.1974.xpi.zip (after downloading remove the .zip extension)

To install locally, go to about:addons and install that file like so:

Don't forget to disable the actual Vue.js devtools extension.

⚠️ 🚨

Also, it would probably a really good idea to enable notifications for either #2000 or the releases, so you don't forget to reactivate and update the actual extension (I won't keep my .xpi updated; you have been warned):

thany · 2023-01-10T10:44:05Z

Is this addon released yet?

If not, it's a good idea to release it to Mozilla only until Chrome is tested properly. Seeing how tremedously annoying this problem is, and all... I mean let's be honest, we've had to cope with this for months.

thany · 2023-01-20T14:56:51Z

@Akryum Just curious: is that fix a temporary workaround, or a proper permanent fix? Seeing how small of a change it is...

Akryum · 2023-01-20T15:27:19Z

It's a proper fix until the extension is fully migrated to Manifest V3 (which doesn't support background pages).

thany · 2023-01-31T13:30:41Z

So why is it closed then? It's not fixed yet, clearly.

djpowers · 2023-01-31T14:34:56Z

Thanks for releasing a new version with this fix @Akryum. I see that the new 6.5.0 update is available on the Chrome Web Store, but Firefox Browser Add-ons is still showing the 6.4.5 release from October 2022. Is there a review process at Mozilla we're waiting on, or does the updated extension still need to be submitted there?

Akryum · 2023-01-31T16:12:04Z

It's still pending review on AMO

djpowers · 2023-02-07T15:40:50Z

For anyone following this issue waiting for the new release, version 6.5.0 containing this fix is now live on AMO: https://addons.mozilla.org/en-US/firefox/addon/vue-js-devtools/versions/

Thanks again to those who helped getting this resolved! 🎉

Akryum mentioned this issue Dec 5, 2022

DevTools crash after a while in FireFox 106 #1950

Closed

dmke mentioned this issue Dec 5, 2022

fix(firefox): stop extension unloading, fix #1974 #2000

Merged

8 tasks

Akryum closed this as completed in ab5623a Jan 20, 2023

djpowers mentioned this issue Jan 26, 2023

Vue Devtools randomly stops working #1697

Open

djpowers mentioned this issue Jan 31, 2023

Latest version not available for firefox. #2023

Closed

abarreir mentioned this issue Nov 15, 2023

Firefox console shows "Attempt to postMessage on disconnected port" from Apollo extension apollographql/apollo-client-devtools#1007

Open

After 2 minutes, it unloads itself #1974

After 2 minutes, it unloads itself #1974

Comments

thany commented Oct 24, 2022 • edited

Vue devtools version

Link to minimal reproduction

Steps to reproduce & screenshots

What is expected?

What is actually happening?

System Info

Any additional comments?

vue-bot commented Oct 24, 2022

ThaDaVos commented Oct 26, 2022

ThaDaVos commented Oct 26, 2022

yi0n commented Oct 26, 2022

golgote commented Oct 26, 2022

Billybob commented Oct 26, 2022

denisgruba commented Oct 26, 2022

dmke commented Oct 27, 2022 • edited

ThaDaVos commented Oct 27, 2022

Androphin commented Oct 27, 2022

thany commented Oct 28, 2022 • edited

thany commented Oct 31, 2022 • edited

Locheed commented Nov 3, 2022

Billybob commented Nov 4, 2022 • edited

lhapaipai commented Nov 7, 2022 • edited

pyrsmk commented Nov 8, 2022

matthewhutchings commented Nov 8, 2022

craigrileyuk commented Nov 8, 2022

cmauf commented Nov 8, 2022

pisandelli commented Nov 8, 2022

cyberlyght commented Nov 9, 2022 • edited

Acartuerk commented Nov 14, 2022

tylerFretz commented Nov 14, 2022

uclnj commented Nov 15, 2022 • edited

matt-smarsh commented Nov 16, 2022

matt-smarsh commented Nov 16, 2022 • edited

dmke commented Nov 17, 2022 • edited

Charl13 commented Nov 17, 2022 • edited

thany commented Nov 17, 2022

thatCodingNoob commented Nov 17, 2022

denisgruba commented Nov 21, 2022

dmke commented Nov 28, 2022 • edited

thany commented Nov 29, 2022

uclnj commented Nov 29, 2022

Akryum commented Dec 5, 2022

dmke commented Dec 5, 2022

Akryum commented Dec 5, 2022

dmke commented Dec 5, 2022

Akryum commented Dec 5, 2022

dmke commented Dec 5, 2022

dmke commented Dec 5, 2022

dmke commented Dec 5, 2022

djpowers commented Dec 15, 2022

dmke commented Dec 16, 2022

dmke commented Dec 22, 2022

⚠️ 🚨

thany commented Jan 10, 2023 • edited

thany commented Jan 20, 2023

Akryum commented Jan 20, 2023

thany commented Jan 31, 2023

djpowers commented Jan 31, 2023

Akryum commented Jan 31, 2023

djpowers commented Feb 7, 2023 • edited

thany commented Oct 24, 2022 •

edited

dmke commented Oct 27, 2022 •

edited

thany commented Oct 28, 2022 •

edited

thany commented Oct 31, 2022 •

edited

Billybob commented Nov 4, 2022 •

edited

lhapaipai commented Nov 7, 2022 •

edited

cyberlyght commented Nov 9, 2022 •

edited

uclnj commented Nov 15, 2022 •

edited

matt-smarsh commented Nov 16, 2022 •

edited

dmke commented Nov 17, 2022 •

edited

Charl13 commented Nov 17, 2022 •

edited

dmke commented Nov 28, 2022 •

edited

thany commented Jan 10, 2023 •

edited

djpowers commented Feb 7, 2023 •

edited