Crash with 2.1b2 in FF4

When taking snapshots of some pages, the entire ff browser crashes.

This page, for example, crashes every time I try to take a snapshot of it: http://investor.palm.com/releasedetail.cfm?releaseid=339495

I have output from the terminal running with debugging enabled and though I cleared the terminal just before clicking the snapshot button so I only am getting the debug output from clicking snapshot button -> crash, it is still "21335 characters too long" to post here ;) Anyway, here are the last few lines. Is there a way to upload a txt file or something; would it be useful to get more of the debug output?


----

[extra output removed — D.S.]

zotero(3): Notifier.trigger('add', 'item', [605]) queued

[wpdDOMSaver.init] ...
[wpdDOMSaver.saveDocumentHTML]: /Users/ellie/Library/Application Support/Firefox/Profiles/k62ps4md.default/zotero/storage/FEEI7UGW/releasedetail.html
  • Same problem, I think -- on first and repeated tries, 'create new item from current page' crashes FF 4.0b7 (Mac OSX) each time. It creates a new empty folder in the Storage directory each time. I did turn the debugger on for the last couple of tries, if the output is of any use (I don't know where to find and how to send it).

    The error report is only since Firefox started and it doesn't capture the crash, sorry, sent a blank report.
  • ankh: Debug output logging doesn't work if Firefox crashes—you need to generate real-time debug output. Only the last couple lines matter.

    If Firefox is crashing from JS code (which this is), it's a Firefox bug. Go to about:crashes, generate a crash report for the relevant crash, and provide a link to the mozilla.org report page.
  • thanks for your reply. here's a firefox crash report:

    http://crash-stats.mozilla.com/report/index/bp-015753b3-d9ca-48b0-b3a7-59feb2101122

    let me know if there's anything else i can do that would be helpful.
  • Thanks. We've committed a workaround for the crash that will make it into 2.1b3, and filed a bug report with Mozilla regarding the underlying issue.
  • oh, thank you!

This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.