User Agent: Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131025151332 Steps to reproduce: Go to http://www.eutelsat.com/en/services/broadcast-media.html Select the following options: Broadcast - Turnkey video solutions (PDF 1.2 MB) Ultra-High Definition (PDF 2 MB) Digital Terrestrial Television (PDF 1.3 MB) Digital Cinema (PDF 4 MB) SNG and Occasional Use (PDF 4 MB) and select Open link in new Tab Actual results: Firefox crashes Expected results: View the new selected content
please open about:crashes and paste the crash id here so that we may see the crash stack. https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs may be helpful.
(In reply to Bob Clary [:bc:] from comment #2) > please open about:crashes and paste the crash id here so that we may see the > crash stack. > > https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs may be helpful. You can find the crash ids below: bp-0b7abe82-ba19-4123-8271-75f052131112 12/11/2013 11:37 πμ bp-6935a68a-794d-4abd-971d-b83a32131112 12/11/2013 10:52 πμ bp-1148436c-5001-4cfc-93d3-5f4702131112 12/11/2013 10:42 πμ bp-ca80dd13-f5b8-4cb0-a466-77d802131112 12/11/2013 10:40 πμ
Ok, these are all empty crash dumps. My first guess is that you are running low on memory opening all of the pdfs at once. No need to keep this security sensitive. Opening it up will get more eyes on it.
Could you check the following crash id as well: bp-bec9432f-1760-468b-a6ed-24a262131112 it makes it all the time in either case
just one frame in the stack: 0 xul.dll xul.dll@0x8237c7 Tom, you can view the crash reports by clicking the link in about:crashes or here in bugzilla, where crash reports are automatically linked if they begin with bp-. Thanks!
Crash Signature: [@ xul.dll@0x8237c7 ]
Couldn't reproduce on FF 25 Win 7 x64. Tom, please check if the issue occurs using Firefox in safe mode (with your addons disabled): http://support.mozilla.com/kb/Safe+Mode Or on a new, empty profile: http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager
(In reply to Tom from comment #5) > Could you check the following crash id as well: > bp-bec9432f-1760-468b-a6ed-24a262131112 > > it makes it all the time in either case This frame appears to be: Crash reason: EXCEPTION_ACCESS_VIOLATION_READ Crash address: 0x2f0ff000 Thread 62 (crashed) 0 xul.dll!_alloca_probe [chkstk.asm : 99 + 0x0] eip = 0x50ff37c7 esp = 0x2f102000 ebp = 0x2f102008 ebx = 0x1729f000 esi = 0x167941a8 edi = 0x00000000 eax = 0x2f0ff000 ecx = 0x2f0fe170 edx = 0x00000d1f efl = 0x00010206 Found by: recovered by external stack walker It looks like maybe we're running out of stack space here.
(In reply to Paul Silaghi, QA [:pauly] from comment #7) > Couldn't reproduce on FF 25 Win 7 x64. > Tom, please check if the issue occurs using Firefox in safe mode (with your > addons disabled): > http://support.mozilla.com/kb/Safe+Mode > > Or on a new, empty profile: > http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager Tom seems to be gone
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.