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

Crashing Firefox 45 and 46 #14

Open
mbaragiola opened this issue Apr 28, 2016 · 4 comments
Open

Crashing Firefox 45 and 46 #14

mbaragiola opened this issue Apr 28, 2016 · 4 comments

Comments

@mbaragiola
Copy link

Hello. This addon is crashing versions 45 and 46 of Firefox.

I haven't tried it on other desktop than Xfce 4.12, but I had tried on both OpenBSD-current and Xubuntu 16.04 LTS.

Disabling the addon stops crashing Firefox.

How to reproduce:

  1. Open Firefox 45 or 46.
  2. Select 'New Window' or 'New Private Window' in the burger menu.
  3. Again, select 'New Window' or 'New Private Window' in the burger menu.
  4. Firefox is now crashed.

Thanks in advance.

@scarlion1
Copy link

Are you also using HTTPS-Everywhere? I seem to be experiencing the same bug but i found it to only happen when both Beef Taco and HTTPS-E are enabled. Firefox 47 on Ubuntu 14.04 here. Beef Taco is 1.3.7.1-signed.1-signed. See EFForg/https-everywhere#4661 (comment)

@mbaragiola
Copy link
Author

mbaragiola commented Jun 25, 2016 via email

@sruggier
Copy link

sruggier commented Nov 6, 2016

+1, my Firefox instance has been entering an infinite loop every time I tried to open a new window, until I disabled Beef Taco. Given how long it has been since the project was last updated, though, I'm not expecting for the owner to start maintaining it again. I'm just confirming the issue to make it easier for other users to troubleshoot the same thing.

1 similar comment
@sruggier
Copy link

sruggier commented Nov 6, 2016

+1, my Firefox instance has been entering an infinite loop every time I tried to open a new window, until I disabled Beef Taco. Given how long it has been since the project was last updated, though, I'm not expecting for the owner to start maintaining it again. I'm just confirming the issue to make it easier for other users to troubleshoot the same thing.

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

3 participants