Localhost:8080 freezes until Privacy Badger stopped

[qskousen]

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.

[qskousen]

Discovered that if I add a mapping for 127.0.0.1 some.domain in my hosts file and access the site using that instead of localhost, PrivacyBadger does not lock up the page.

[ghostwords]

Hello and thanks for getting in touch!

Could you share what it is being served at localhost:8080, either in public or private? I'd like to try to reproduce the issue. Privacy Badger should never cause unresponsive pages.

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.

Discovered that if I add a mapping for 127.0.0.1 some.domain in my hosts file and access the site using that instead of localhost, PrivacyBadger does not lock up the page.

Interesting! This may be a bug in one of our URI/hostname parsing utilities.

This is related to #817.

[ghostwords]

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?

[qskousen]

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.

[ghostwords]

All good, thanks for confirming!