We made this change back in Nov to enable us to test the browser hang detector - Bug 705365. We ended up leaving in this change which obviously has resulted in a higher number of plugin crashes. Product thinks we should change it back until we better understand what the right number is. Bug 705365, comment #6 implies that we should have taken it out for Beta. We would like this removed for Firefox 11 so adding the tracking flag.
% pwd /Users/akeybl/Mozilla/mozilla-beta $ hg backout 6f079f13c06a https://hg.mozilla.org/releases/mozilla-beta/rev/3f12a90bf9d798a830e8fa833be569795ec1135c
Alex, can we get this changed in Aurora and Nightly as well?
It looks like numbers on beta are coming down to normal levels - Alex, could you please check this into aurora and central as well?
I've done this for Aurora, but Sheila mentioned she'd get in touch with bsmedberg about backing it out on m-c to make sure we have consensus. https://hg.mozilla.org/releases/mozilla-aurora/rev/f7dee7d1368a
(In reply to Alex Keybl [:akeybl] from comment #4) > I've done this for Aurora, but Sheila mentioned she'd get in touch with > bsmedberg about backing it out on m-c to make sure we have consensus. From #breakpad (times in CET): Feb 29 16:38:26 <KaiRo> bsmedberg: What's your opinion on https://bugzilla.mozilla.org/show_bug.cgi?id=725869#c4 - should we do this revert for trunk as well? (I think we should) Feb 29 16:38:30 <firebot> Bug 725869 nor, --, mozilla13, nobody, REOP, Set the plugin hang timeout back to 45s Feb 29 16:39:56 <bsmedberg> KaiRo: it's a product decision, but it seems Asa has made it Feb 29 16:39:58 <bsmedberg> so yeah I guess that means we should do this revert to 45s on trunk as well. Alex?
(In reply to Robert Kaiser (:email@example.com) from comment #5) > I guess that means we should do this revert to 45s on trunk as well. Alex? Agreed - sending over to Benjamin for the final backout of bug 722394 on m-c.