Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension Context Invalidated #611

Open
Lagicrus opened this issue Sep 30, 2020 · 1 comment
Open

Extension Context Invalidated #611

Lagicrus opened this issue Sep 30, 2020 · 1 comment

Comments

@Lagicrus
Copy link

@Lagicrus Lagicrus commented Sep 30, 2020

Description

After Ending the Ghostery Process (In Chrome via Chrome's Task Manager) and restarting it, the dev console is flooded with the following error
image
Which is spammed every 0.2s when actively using the said page.
It is then "fixed" after reloading the page.

Expected Behavior

No console errors especially spammed ones.

Actual Behavior

Spammed console errors.
Possible memory leak as well caused? Can see 1GB of memory usage from the extension, hence why I kill it again.

Steps to Reproduce

  1. Open Chrome (with Ghostery Active)
  2. Open a page, say google.com
  3. Open DevTools (Ctrl+Shift+i/Via the menu More Tools->Dev Tools)
  4. Go to the Console tab
  5. Notice no errors of this type
  6. Open Chrome task manager (Shift+Esc/Via the menu More Tools->Task Manager)
  7. Find Extension: Ghostery
  8. Click it
  9. Click the End Process button
  10. (Optional) Reload Ghostery
  11. Notice that DevTools Console tab has a few errors.
  12. Simply scroll/click/barely use the page
  13. See an error spam

Versions

  • Browser: Chrome 85.0.4183.121
  • OS: Windows 10 Version 10.0.20221 Build 20221
  • Node: N/A
  • NPM: N/A
@Lagicrus
Copy link
Author

@Lagicrus Lagicrus commented Sep 30, 2020

This is also reproducible in the Chrome Dev build (87.0.4270.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant