-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Localhost:8080 freezes until Privacy Badger stopped #2889
Comments
Discovered that if I add a mapping for |
Hello and thanks for getting in touch! Could you share what it is being served at You could also try to narrow down what exactly about the page results in unresponsiveness, such as by removing parts of the local app until the problem goes away.
Interesting! This may be a bug in one of our URI/hostname parsing utilities. This is related to #817. |
I just looked at the performance profile (thank you!). I see most of the time was spent in the DDG extension, not in Privacy Badger. Is that right? |
I have made a mistake 🤦 So sorry, I don't know what led me to think this was PrivacyBadger's fault. I double checked and it is indeed the DDG extension that is freezing the page. |
All good, thanks for confirming! |
What is your browser and browser version?
Firefox 111.0 Linux Mint
What is broken and where?
Navigating to my localhost:8080 page causes the page to become unresponsive until Firefox reports that PrivacyBadger is slowing down the browser and gives me an option to stop it. Stopping it fixes the slowdown. I have captured a performance profile:
https://profiler.firefox.com/public/1rns1z2dwrmf127p2meyp3hpfmtn24wepshre78/calltree/?globalTrackOrder=01&implementation=js&thread=1&v=8
The culprit domain and debugging steps don't seem to apply here so I have not included them.
Edit: Forgot to mention that having PrivacyBadger disabled for the domain does not resolve the issue.
The text was updated successfully, but these errors were encountered: