Intro
I have deliberately posted this here rather than in the KB section as I think it deserves the higher exposure it will get here.
Any opening comments anyone ?
- I think as an absoluter minimum we should monitor closely any threads where users try this method (Possibly open an etherpad)
- and try to gather crash reports for the cases where this method helps. (Always assuming the apparent success of "Carm" is in fact reliably reproducible)
The solution is rather out of our ordinary scope, but then Flash Player problems are extensively reported and notoriously hard to solve. We have discussed Flash & Flash KBs endlessly already, but this proposal is a radical and different approach.
- Is this something the new HelpDesk staff should get directly involved with testing and co-ordinating ?
(I will ping Patrick by pm) - I will quote Carm's full post /questions/968190?page=6#answer-510624 next in this thread, with my invitation, to discuss this here.
- Note that single thread alone is a 6 page thread with approaching: 700 me too votes, 45,000 views, and over100 posts
- At the same time may I ask is it any good trying to promote the new Flash Reporter for some of the advanced users that we may manage to recruit in testing out this solution. (i.e user willing & able to try other versions of Firefox and multiple profiles, and to reproduce,or at least report crashes with crash IDs)
Edit, IIRC the new crash reporter is still active but only on pre-Release versions and not being moved up the train to Releases. Not able to locate the relevant bug at present but did find this note
- https://crash-analysis.mozilla.com/hang-reports/
- in turn linking to the one year old https://wiki.mozilla.org/Socorro/Hang_Processing_Proposal and a list of 2012 reports.
Modificado por John99 em