Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

When I try to Print Edit (Firefox add-on) anything on the http://www.tomshardware.com/ website Firefox crashes.

more options

I am using the Print Edit add-on to Firefox (version 47.0.1). I believe it is version 16.8, as I have the default automatic updates and it was last updated on May 23, 2016.

When I try to Print Edit anything on the http://www.tomshardware.com/ website Firefox crashes with the Mozilla Crash Reporter popup. So far the problem seems limited to the tomshardware site. Print Edit works on all other sites I have used it on.

I am using the Print Edit add-on to Firefox (version 47.0.1). I believe it is version 16.8, as I have the default automatic updates and it was last updated on May 23, 2016. When I try to Print Edit anything on the http://www.tomshardware.com/ website Firefox crashes with the Mozilla Crash Reporter popup. So far the problem seems limited to the tomshardware site. Print Edit works on all other sites I have used it on.

All Replies (1)

more options

I am having "print" problems in Firefox Profiles that have Print Edit installed since Firefox 45 was released. But I have so damn many extensions installed it is hard to troubleshoot my problem, which is "error messages" and not being able to print. Easier to just open another Profile (with Print Edit installed) and use that Profile where it works; which leads my to think the problem isn't with Print Edit specifically.

My advice is to install an older version of Print Edit from here: https://addons.mozilla.org/en-US/firefox/addon/print-edit/versions/ Hopefully that will stop the crashing for you - but you will need to turn off updates for that extension in the Addons Manager.

And email the developer of Print Edit to notify him of your problem with crashing. But be nice, as he is having to cope with fixes related to e10s problems (the 16,8 version fix) and we don't want to piss him off, and possibly see fixes stop coming - IOW, he gives up and walks away from this extension altogether. I gotta say if that problem of yours is related to using WinXP and not newer versions of Windows. he shouldn't waste his time trying to fix it. Sorry, but I left WinXP behind a little over a year ago for Win7.