Coupon Printer Manager plugin has crashed
I am running Windows XP SP3 and all updates are current.
For weeks, running 7.0.1, 8.0.1 or 9.0.1, whenever I try to print coupons at the www.coupons.com website, I have difficulty and consistently I receive the following Firefox ERROR message...
"The Coupons Inc. Coupon Printer Manager plugin has crashed"
...and I always SUBMIT a REPORT to Mozilla.
This website is suppose to invoke the following plug-ins...
Coupons Inc., Coupon Printer Manager 4.0.1.3 Coupons Inc., Coupon Printer Manager 4.0.0.7
...and using Task Manager I watch to see if the Image column shows one or two plug-ins appear - of course, I don't know which ones - see below for additional info. Most of the time only one plug-in appears and then the website asks me to INSTALL the software (again). When two plug-ins appear (again, I do not know which), things run okay for the first coupon - however around 50% of the time I am unable to print a second, third, etc, coupon.
Regarding add-ons, I have the following:
PLUG-INS Coupons Inc., Coupon Printer Manager 4.0.1.3 Coupons Inc., Coupon Printer Manager 4.0.0.7 Java Deployment Toolkit 6.0.300.12 6.0.300.12 Java Platform SE 6 U30 6.0.300.12 QuickTime Plug-in 7.7 7.7.0.0 Shockwave Flash 11.1.102.55
EXTENSIONS Adblock Plus 2.0.3 Free Download Manager plugin 1.5.5
APPEARANCE FOXSCAPE 4.01 Default 9.0.1 (disabled)
I have disabled each of these add-ons to see if anything improves, but nothing does. This does not surprise me since I have been running the same ADD-ONS for months and this problem has only started happening over the past few weeks.
I have uninstalled the Coupon Printer plug-ins, scrubbed my Registry, and then reinstalled them (with FF closed, as well as opened, of course), and that does not help either.
Sure would like to RESOLVE this FF problem.
I am wondering if there's a PLUGINS setting that needs tweaking, and on that note, I have tried setting...
dom.ipc.plugins.java.enabled
...to TRUE (where default is false) and that does not help either.
The following screen shot shows my about:config / plugin details > http://tinypic.com/r/10dv3v7/5
Hopefully, others have experienced the same problem and found a workaround or fix.
Thanks,
CurlySue :o)
Chosen solution
Sorry, I don't know where to look up messages such as - EXCEPTION_ACCESS_VIOLATION_READ - but even if I did, that wouldn't get us any closer to fixing the problem with that plugin.
https://crash-stats.mozilla.com/products/Firefox - put the Crash ID in the search box in the upper-right corner of that page.
Or, type about:crashes in the Location Bar and hit Enter.
You will get a hyperlink list of your Crash Reports that you can click on and be taken directly to the actual crash report page, after waiting for it to load the first time it is called up. I had to wait almost 3 minutes to see your report - six loading / wait cycles to call it up.
All Replies (6)
It would be nice if we could see the crash reports that were sent to Mozilla - the Crash Report ID numbers.
https://support.mozilla.com/en-US/kb/Firefox%20crashes#w_get-help-fixing-this-crash
Type about:crashes in the URL bar and hit Enter.
- Middle-Click the hyperlinks to bring up each Crash Report page in a new Tab; each page may take a few minutes to load.
- Then copy'n'paste the URL of each of those reports into the message box here.
- We'll see if we can help you figure out what is causing those crashes to happen.
If you can't open Firefox or keep it open long enough to get the Crash Report ID's, even in the Firefox Safe Mode - see the section entitled - You can't open Firefox because it crashes at startup even in Safe Mode:.
Sorry it took me so long to get back to you, family issues.
I have SEVERAL reports for your review, including the follwing Crash Report ID taken from different PCs that suffer the same Coupon Printer-related problem I described over 3 weeks ago in this forum...
2012-01-11 Crash ID: bp-b7c6e33f-d12b-481f-aca0-546b12120111
2012-02-17 Crash ID: bp-c4077e92-719a-453b-b046-e4b802120217
Other DATES Crash ID: bp-9cb6ff8d-0acc-4490-bfa8-c48bf2120217 Crash ID: bp-a855f8e7-964c-49b8-a049-54aba2120217 Crash ID: bp-51be502e-6bfb-4c31-8738-1f5302120217
I hope these Crash ID and their associated Crash Reports HELP me RESOLVE this Firefox/Coupon Printer PROBLEM.
Thank you for your assistance.
CurlySue :o)
Sorry, a resolution isn't going to easily or come from Mozilla.
4 out of 5 of those crashes were directly caused by the Coupons, Inc. Coupon Printer DLL = npMozCouponPrinter.dll
The developer of that plugin is going to have to fix it. Contact the Coupon website to find out how to report a bug with that plugin.
https://crash-stats.mozilla.com/report/index/b7c6e33f-d12b-481f-aca0-546b12120111
https://crash-stats.mozilla.com/report/index/c4077e92-719a-453b-b046-e4b802120217
https://crash-stats.mozilla.com/report/index/51be502e-6bfb-4c31-8738-1f5302120217
https://crash-stats.mozilla.com/report/index/9cb6ff8d-0acc-4490-bfa8-c48bf2120217
This report doesn't specifically indite that plugin, but points to a general plugin fault.
https://crash-stats.mozilla.com/report/index/a855f8e7-964c-49b8-a049-54aba2120217
Thank you for your SUPER FAST response, edmeister!
Bummer on the fix. :o(
I do find the reference to EXCEPTION_ACCESS_VIOLATION_READ associated with the plugin Version: Filename: npMozCouponPrinter.dll
Once I submit a Crash Report, how do I find the detailed information (as noted above) as you have so kindly provided in your reply?
Would it be as simple as adding the Crash Report ID to the following URL > https://crash-stats.mozilla.com/report/index/CrashReportID
Thanks again, Ed. :o)
CurlySue
Seçilmiş Həll
Sorry, I don't know where to look up messages such as - EXCEPTION_ACCESS_VIOLATION_READ - but even if I did, that wouldn't get us any closer to fixing the problem with that plugin.
https://crash-stats.mozilla.com/products/Firefox - put the Crash ID in the search box in the upper-right corner of that page.
Or, type about:crashes in the Location Bar and hit Enter.
You will get a hyperlink list of your Crash Reports that you can click on and be taken directly to the actual crash report page, after waiting for it to load the first time it is called up. I had to wait almost 3 minutes to see your report - six loading / wait cycles to call it up.
Thank you so very much for your kind, comprehensive as extraordinarily FAST replies, edmeister. :o)
With kindest regards,
CurlySue :o)