836711 - Crash in outlook (hotmail.com) composing a new message or replying/resending an old one

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[prueboblog]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:21.0) Gecko/20130130 Firefox/21.0
Build ID: 20130130030907

Steps to reproduce:

Firefox crash when I want to compose a new message in mail.live.com (aka hotmail or more recently outlook). Also, it crashes when I want to resend or reply some message.

Firefox nightly (21) on Win7. In linux works fine.


Actual results:

Crash!!


Expected results:

not crash :P

Comment 1

[Scoobidiver (away)]

Please provide the crash ID from the about:crashes page.
Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?

Comment 2

[prueboblog]

There's no bug report to the crashes (I crashed three times today, but there's no new entries in the about:crashes).

Windows report says is mozjs.dll fault.

Comment 3

[prueboblog]

Attachment: crash...

Is the screenshot of the "crash moment"

Comment 4

[Scoobidiver (away)]

Please answer for the safe mode.

Does it happen with the 32-bit build? If yes provide the crash ID, if no try to get a stack trace with the 64-bit build (see https://developer.mozilla.org/docs/How_to_get_a_stacktrace_with_WinDbg)

Comment 5

[prueboblog]

Wait!! I'm not sure, but it seems that you must close this bug. In safe mode seems to work fine. Maybe there's a bug of noScript or else... (I haven't other extensions installed and noScript change the scripts behaviour...)

Comment 6

[Scoobidiver (away)]

Maybe NoScript highlights a bug in Firefox so try to identify clearly the culprit (HW acceleration, NoScript...) and answer to the end of comment 4.

Comment 7

[Robert Kaiser]

I find it strange that this is a crash that our own Crash Reporter doesn't catch but gets caught only on the Windows side.

I'd love to hear what add-on is causing this, as we might need to debug why it makes the Windows reporter appear instead of our own one.

Comment 8

[prueboblog]

Well, I think that is the layer acceleration. When I set layers.acceleration.disabled to true it works fine. I will try to debug and send a trace if I can.

Comment 9

[(not currently active) Ted Mielczarek]

Yes, finding things that we don't catch in Breakpad is very important. If you find consistent steps to reproduce I am very interested.

Comment 10

[Scoobidiver (away)]

(In reply to Robert Kaiser (:[e-mail]) from comment #7)
> I find it strange that this is a crash that our own Crash Reporter doesn't
> catch but gets caught only on the Windows side.
It happens a lot with 64-bit builds.

Comment 11

[prueboblog]

(In reply to prueboblog from comment #8)
> Well, I think that is the layer acceleration. When I set
> layers.acceleration.disabled to true it works fine. I will try to debug and
> send a trace if I can.

It's a really really rare behaviour. I installed windbg. Executed with windebug as the how-to guide says, firefox don't crash.

I quit debug and try several times to get the crash, even I restarted the pc. Now, there's no bug. Becouse I didn't change the config any more (I have extensions, plugins and layer acceleration active), and there haven't any update for firefox or windows, I have no idea of the cause. Maybe was some windows component causing the bug? maybe the installation of the windbg change some internal configuration or overwrite some library or else?

Comment 12

[Scoobidiver (away)]

Let's close as workforme per comment 11.

Comment 13

[Robert Kaiser]

Oh, this is win64? In that case, we don't support those builds officially anyhow at this point.

Comment 14

[Fr3dY]

I'm suffering this bug, using both official Firefox builds v20 final and v21 beta.
Crash Report activates and sends report successfully.
Latest sent report ID is bp-8165d4f7-318a-48f9-b06e-c95852130407

Comment 15

[Scoobidiver (away)]

Fr3dY, you hit bug 851934. If you have reliable steps to reproduce, please comment in that bug.

Comment 16

[Axel]

Same for me here. Firefox 23.0.1.

Here are my crash IDs:

bp-ccde11df-76da-43d0-babe-3528a2130829
bp-5e2fa210-d8db-4547-a9ec-99d6b2130822
bp-c3f1f4b0-6a2b-4e95-8861-aa3b72130822
bp-68701842-b7c5-4309-8ced-449982130821