Crash on Opening Email




DOM: Events
2 years ago
2 years ago


(Reporter: Vikas Raunak, Unassigned)


42 Branch
Windows 8.1

Firefox Tracking Flags

(Not tracked)




(1 attachment)



2 years ago
Created attachment 8637051 [details]
The crashed tab leads to the crash of all open tabs.

I installed the Nightly build and tried to open the mail for Sync, but the browser crashes every time I try to open the mail. Restore tabs also leads to the same behavior. 

I tried again using opening (not as a part of sync sign-in process) and again the tab crashed. In the first time, the browser crashed and I had to re open it while after the first time, a dialog box started appearing.
Reporter: Please type about:crashes in the URL bar and paste the report IDs here
Group: core-security
Flags: needinfo?(v.raunak)

Comment 2

2 years ago
Bug 1186340

(In reply to Marcia Knous [:marcia - use ni] from comment #1)
> Reporter: Please type about:crashes in the URL bar and paste the report IDs
> here

When you access and log in to view the emails, clicking on a mail leads to crash (all the tabs). Please let me know If I am to provide more details and contribute in the process. Thanks.
Flags: needinfo?(v.raunak)

Comment 3

2 years ago
We need to know the link to your crash reports: you can get these by clicking on the crash reports in about:crashes.
Component: Build Config → Untriaged
Flags: needinfo?(v.raunak)

Comment 4

2 years ago
Report Ids of the Crashes are:
Flags: needinfo?(v.raunak)

Comment 5

2 years ago
Sorry, plz see this:

Report Id: bp-60fc457e-8e09-4cea-ad9a-522c72150726


Also, some other crash reports occurring due to the same/similar reasons (Opened outlook mail, gmail) are:

Report ID 	                              Date Submitted
bp-60fc457e-8e09-4cea-ad9a-522c72150726     26-07-2015	17:21
0e7ef349-bbf2-4b7c-ae78-3218e2acb38f        22-07-2015	13:37
bp-ab27469d-d2d3-4706-8791-a44ac2150722     22-07-2015	13:37
521f8a8a-903c-48f0-9a19-c95080142dbf        22-07-2015	13:36
bp-7d323436-d422-4a33-8163-139482150722     22-07-2015	13:19
bp-c6966d9c-4303-45a6-bb18-f94ff2150722     22-07-2015	13:19
c4206260-6d8e-4c1f-b46c-d68b39be94cc        22-07-2015	13:13
2c41f5cd-70b5-4c1e-8e87-56a223f15c37        22-07-2015	13:11
bp-ec9e47c6-8318-41fc-8f4e-716672150722     22-07-2015	13:11
c52369b4-b9fa-4950-b515-914e0868c0ef        22-07-2015	13:11
bp-05e03f47-604a-4351-af8c-2521a2150722     22-07-2015	13:07
a9fd88d6-be28-424d-921a-6dac14f15231        22-07-2015	13:06
bp-3722170f-0fb6-46d9-a6af-b1fa12150722     22-07-2015	13:06
1ead2ee6-1121-4054-9c25-5ecc0790992c        22-07-2015	13:05

Thanks for your help. Please let me know if I can contribute in the process.

Comment 6

2 years ago
I suspect this is e10s-specific.  Vikas, can you try disabling e10s in nightly by unchecking Options > General > Enable multi-process Nightly and restarting?
Component: Untriaged → DOM: Events
Flags: needinfo?(v.raunak)
Product: Firefox → Core

Comment 7

2 years ago
Yes, after disabling Multi-process nighly, it worked fine. Also, in the update received for Nightly, it seems to fix the problem even when Multi-process is enabled.
Flags: needinfo?(v.raunak)

Comment 8

2 years ago
ok, I'm going to mark this WORKSFORME, and if you see this again please reopen or let me know. Thank you for reporting the issue!
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.