Both those crashes were reported from Firefox 32.0.1, as stated in each crash report.

Does that happen if you disable Cookie Clicker?

As far as letting a computer run overnight, I have run 3 different "desktop" PC's 24/7/365 except for shutdowns to do periodic maintenance (like internal cleaning), perform hardware upgrades, while reinstalling Win98 or W2K, or during power outages when the UPS ran out of "juice". And I have left Firefox open for days at a time with few problems. The effects of 24/7/365 - more electricity consumption - but longer PC life due to eliminating cool down / warmup cycling, no problems with hard drives as they stay warm even if they are set to go inactive after (say) 15 minutes. I did "lose" an expensive monitor once due to crappy capacitors in the internal power supply due to leaving it in Standby rather then shutting it off - when cpapacitors are poorly made their life is "measured" in so-many thousands of life before they "pop". A handful of new premium grade capacitors and about 5 hours of my time and it was up and running again, for the last 4 1/2 years, but I do shut it down overnight.

Both those crashes were reported from Firefox 32.0.1, as stated in each crash report.

Not sure why the 9/19 one is reporting the wrong version, maybe that is another bug. See attached capture of my FF version update history. I moved to 32.0.2 on 9/18.

Does that happen if you disable Cookie Clicker?

Well, first, Cookie Clicker is not an add-in, extension, etc. it is a Javascript based game (http://orteil.dashnet.org/cookieclicker/). Second, The point of this thread is to get Cookie Clicker working again, as it did before the update, so closing it wouldn't solve the problem...

It does remind me of the classic joke though... Patient: "Doctor, it hurts when I do this". Doctor: "Then don't do that."

Thanks!

P.s. - the image uploader here won't work... It just sits on a spinning icon forever saying "Uploading "FF_Update.jpg"..." :/

OK, new morning report...

Last night I left cookie clicker open but left a different tab "in focus", hoping that this might help. FF had not crashed this morning but it is not performing well. When going to CC, it is now very "choppy" and every few clicks it hangs on the spinning color wheel.

This behavior reminds me of a memory leak type problem. Any way to examine the current memory state of FF?

Also worth noting, the performance drag only occurs when that tab is in focus. Otherwise FF performs fine. So I need to see data on just that FF process? (don't different FF tabs run in separate threads now?)

Next steps I have taken:

1. saved progress, reloaded tab. 2. right click on page and go to "view page info" 2.a. Under Media, scrolled to find ads (usually .swf flash) and blocked images from those sites. 2.b. repeat 1-2a multiple times 2.c. Under view page info -> permissions, blocked Adobe Flash for just this site.

So far performance is back up. We'll see how it holds up overnight.

No new steps since the above. left the window open and in focus last night and performance was fine this morning. I am suspecting now that the culprit may have been flash-based ads and that specifically blocking flash for this site is the best step since the game itself isn't flash-based.

Well darn. Total crash last night, frozen/locked up computer this morning that had to be restarted. Here is what was in the console log:

9/30/14 8:47:28.000 AM kernel[0]: process firefox[21078] thread 5623583 caught burning CPU! It used more than 50% CPU (Actual recent usage: 77%) over 180 seconds. thread lifetime cpu usage 321.341486 seconds, (295.579870 user, 25.761616 system) ledger info: balance: 90008770014 credit: 299479435974 debit: 209470665960 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 115511909214

9/30/14 8:47:28.202 AM ReportCrash[21153]: Invoking spindump for pid=21078 thread=5623583 percent_cpu=77 duration=117 because of excessive cpu utilization

/