Created attachment 647136 [details] screenshot of error On opening large xhtml documents, Firefox crashes out with "A breakpoint has been reached". 'Large' in this case means about 5MB of markup linking to 600+ PNG images totalling around 1GB. Markup is moderately complex in terms of nesting etc, but primarily consists of plain text (UTF-8) in divs and spans with a few tables. In safe mode, FF does not crash, but does hang; have not observed the problem prior to 14.x, but have been able to cause it in v13.? (under Win7 x64 on a machine with 8 cores/12GB ram) by opening same document. Have previously seen same crash with other documents, but only in the last few weeks. Opera and Chrome open same document with no trouble at all - haven't been able to test in IE owing to quirks of local config.
Do you have an URL to provide? Does it happen with a new profile (see https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles)? Can you provide a stack trace of the hang (see https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report#Alternative_ways_to_get_a_stacktrace)?
Sorry, should have said - these are documents on local hard drives. I won't be able to provide samples, since they're renditions of as-yet unpublished textbooks. I'll get a stack trace and test under a clean profile - will report back later; I'll also test opening them through http.
bp-f368be86-1822-412f-a0cd-731682120731 31/07/2012 09:22 bp-39c6b938-c4d8-489b-a637-66ffe2120731 31/07/2012 09:20 bp-37e1ec52-8e89-44d9-a7fd-c6fcf2120730 30/07/2012 15:21 bp-ec3ccc73-7097-4b1e-b7fe-fd2c92120730 30/07/2012 12:49 bp-721d45aa-7812-4575-a6b1-b3ab42120730 30/07/2012 12:46 bp-7d7661c2-1d78-4252-bf3f-87a162120730 30/07/2012 12:45 Most recent two are with a new, clean profile. And finally, one opening the file via a local webserver (same behaviour): bp-3da041b8-d3b4-4350-8ce2-5962f2120731 31/07/2012 09:34
All these crash reports are non-exploitable. Please provide a valid stack trace using the link in comment 1.
Sorry, my fault - at the limits of my technical understanding here :) Have attached a stack trace for the crash. Hope it's more helpful.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 764342
You need to log in before you can comment on or make changes to this bug.