If you visit about:crashesthen you can click through to the processed version on Mozilla's site, which will have already looked at it and decided if it is a known issue or not.
Tom On 29/01/16 09:49, Maxim Solodovnik wrote:
then examine it using winedbg (found no other way)
