-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
"This extension is slowing down Google Chrome. You should disable it to restore Google Chrome's performance" #2519
Comments
is this really an issue or just Chrome trying to persuade people to not use it like they did when they booted it off the chrome web store? |
@mneunomne status? |
@dhowe I wasn't able to reproduce this issue afterwards. It only appeared when force-testing the extension while in development. Maybe I should close this issue in the mean time while it doesn't appear in "normal" circunstances. |
It was happening with me too, it was causing Chrome to experience severe memory leaks when I was leaving it open for a while. I switched over to the Edge version and haven't had that issue there. |
thank you @blazingwinter, I will look into it once again. Could you share the context in which this occured? Did you have many collected ads, many tabs, etc? |
Generally, it only happened when I had a YouTube livestream going. The live chat for sure was a major cause in contributing to the memory leak, and usage dropped a good bit when I closed it, however it didn't prevent the eventual memory leak. I disabled AdNauseum and tried again, memory leak with the chat open, however no memory leak ever happened when I closed it altogether. Memory usage was still high, even for Chrome standards. But when I switched to Edge, I haven't had this issue again, both with and without AdNauseum enabled. I don't believe I had many collected ads at the time, I reinstalled the extension when this issue first arose, and it's pretty rare for me to have more than 3 or 4 tabs open at a time. |
This warning appeared on Chrome. I've seen it before, usually not while using it reguarly, but while testing different features extensively.
The text was updated successfully, but these errors were encountered: