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

Latest version seems to be broken in Edge, causing high CPU usage and page loading failures #161

Open
bsiegel opened this issue Jul 23, 2024 · 2 comments

Comments

@bsiegel
Copy link
Contributor

bsiegel commented Jul 23, 2024

I'm using the Chrome version of this addon in Microsoft Edge. After updating to 0.9.2, in my browser pages appear to never stop loading, CPU usage is extremely high, and in the console I see a constant spam of this error message:

GET chrome-extension://invalid/ net::ERR_FAILED

In the network tab, it showed the source of these requests as coming from this extension in popup.js Line 166:

 this.src = chrome.runtime.getURL('img/default_favicon.png');

I confirmed that disabling this extension fixes the issues.

@bsiegel bsiegel changed the title Latest version seems to be broken, causing high CPU usage and page loading failures Latest version seems to be broken in Edge, causing high CPU usage and page loading failures Jul 23, 2024
@Pitmairen
Copy link
Owner

In the network tab, before the error messages, do you see any lines starting with data:image/... or something similar? And if you click these lines and open the "preview" tab, do you see the icons?

The line with img/default_favicon.png is a fallback icon in case the regular icons fail to load. But it looks like there may be something wrong with getting the icons, so the fallback probably also fails, and it ends up in a loop.

If you click the extension icon => Manage Extension => Enable developer mode => click the Inspect views service worker line.

Do you see any error messages in the console or network tab in the inspect window?

@Pitmairen
Copy link
Owner

Should be fixed in version 0.9.3, which should be available shortly.

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

No branches or pull requests

2 participants