Privacybadger: PB 2.0 on Firefox 50.0.2 (Linux) breaks IRCcloud.com

[ghost]

As of the latest (newest) version of Privacy Badger (2.0), running on Firefox 50.0.2 (standard distributed with Fedora 25) causes IRCcloud.com to never get past its loading state after signing in.

Disabling the Add-On allows the site to load fine.

Interestingly, there are 0 items blocked, and even with the add-on "disabled for this site" (IRC Cloud) the page still doesn't load.

[ghost]

Oh, and I did try the uninstall-and-reinstall suggestion from other issues and Twitter, and sadly that didn't fix the problem.

[spinda]

Experiencing the same issue; reinstalling doesn't fix it for me either.

https://gyazo.com/1f75c19d0265b06b9292fe5a2ce62966

Firefox Developer Edition 52.0a2 (2016-12-13)

[ghost]

Reproduced same problem on Firefox 50.1.0 (up to date) on OS X 10.12.1.

[groovecoder]

Looks like the same ERROR.captureStackTrace issue causing https://github.com/EFForg/privacybadger/issues/1050 and fixed in https://github.com/EFForg/privacybadger/pull/1053. Suggest closing this as duplicate and merging https://github.com/EFForg/privacybadger/pull/1053 ASAP.

[cooperq]

This should be fixed by version 2016.12.15.1 please re-open if not.

[tigt]

I just had this issue, after FF Nightly crashed (as it's wont to do). I previously had www.irccloud.com whitelisted and things worked okay.

Firefox OSX 54.0a1 (2017-01-24) (64-bit)
Privacy Badger 2017.1.24.1

I've tried reproducing, but unfortunately this seems non-deterministic.

[tigt]

CAUGHT ONE. I have the output of the JS and browser consoles at https://gist.github.com/tigt/c97b56d780864cc01d1a1a6d70e2ef15

If I had to guess, the Chrome-specific code may have leaked over again due to Firefox enabling Chromium features for their WebExtensions push.

[pimeys]

Having the same issue here. I can see the JS error:

TypeError: ERROR.captureStackTrace is not a function[Learn More]

Firefox 50.1.0 + PB 2017.1.24.1

[spinda]

I'm also experiencing this, on Firefox Developer Edition 52.0a2 (2017-01-20) (64-bit) (Windows 10), with Privacy Badger 2017.1.24.1. Could this issue be reopened? (cc @cooperq)

[ghostwords]

This should be fixed again with Privacy Badger version 2017.1.26.1, released a few minutes ago.