User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20170907220212 Steps to reproduce: 1) enter https://www.flipkart.com in address bar 2) press enter Actual results: FF-nightly browser crashed Expected results: it should not be crashed in any condition.

Why is this bug marked as security sensitive? Also, I can't reproduce and there is no crash report mentioned.

:Madhuri, could you open about:crashes and give the crash id ?

Please provide a crash report link from about:crashes.

(In reply to Calixte Denizet (:calixte) from comment #2) > :Madhuri, could you open about:crashes and give the crash id ? (In reply to :Gijs from comment #3) > Please provide a crash report link from about:crashes. Sure, Giving the crash report link below - https://crash-stats.mozilla.com/report/index/bp-b2baad4d-c8cc-4ce8-9bf6-3d9c90170908 https://crash-stats.mozilla.com/report/index/bp-ed63935f-513d-4a20-992c-b46e40170908

(In reply to Pascal Chevrel:pascalc from comment #1) > Why is this bug marked as security sensitive? Also, I can't reproduce and > there is no crash report mentioned. I have attached the crash report above now. How to remove security sensitive thing ?

(In reply to :Gijs from comment #3) > Please provide a crash report link from about:crashes. Report ID Date Submitted bp-b2baad4d-c8cc-4ce8-9bf6-3d9c90170908 08-Sep-17 3:25 PM bp-2a90c6f8-03aa-4e40-a508-0ed220170908 08-Sep-17 3:25 PM bp-ed63935f-513d-4a20-992c-b46e40170908 08-Sep-17 3:19 PM bp-1219a44d-47c9-4b72-b68c-9d2c10170908 08-Sep-17 3:19 PM bp-7f251d59-477e-4ad7-9676-c7aab0170908 08-Sep-17 3:18 PM bp-b8f86afb-954f-4974-93a8-56e000170908 08-Sep-17 3:18 PM bp-06682626-fbaa-4e6a-a4c2-f20130170908 08-Sep-17 3:17 PM bp-8acfcfb9-bf8c-47a8-9fc6-80eed0170908 08-Sep-17 3:17 PM bp-b793007a-a600-48c8-a2db-09fbc0170908 08-Sep-17 3:16 PM bp-e91f4b25-eec9-48c0-a49e-e69550170908 08-Sep-17 3:16 PM

still not resolved with build ID 20170908100218 OS : win 10X64 latest crash report : https://crash-stats.mozilla.com/about/throttling

(In reply to Madhuri from comment #8) > still not resolved with build ID 20170908100218 OS : win 10X64 > > latest crash report : https://crash-stats.mozilla.com/about/throttling Yes, because the duplicate is still open, but the duplicate is where fixes will be tracked, not here. No point having 2 bugs open for the same issue, and while the other bug is open, it's not useful to state that the issue is not fixed yet - that's expected.

[bugday-20170913] status-ff57.0a1 : VERIFIED & FIXED. Managed to reproduce the issue on Firefox Nightly under Windows 10 X 64. The issue is no more reproducible on Firefox latest Nightly [BuildID : 20170913220121 , 57.0a1 (2017-09-13) (64-bit)]