945175 - Firefox crashed (nightly 28.0a1) in [@ xpc::PrincipalImmuneToScriptPolicy ]

Status: VERIFIED FIXED

(Core :: General, defect)

Description

[Ashish Namdev]

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20131201030203

Steps to reproduce:

Open Nightly ,
open gmail
open FB
used firebug to debug page


Actual results:

Nightly 28.0a1 crahsed

Crash ID : cc981b4e-e953-4d04-a11f-543d42131202


Expected results:

It should run firebug to debug issue on web page

Comment 1

[Loic]

Are you able to repro the bug with a clean profile and without Firebug?

Comment 2

[Ashish Namdev]

Without Firebug it's very random ,

but with Firebug again got same issue  :

UUID : 875820cf-1ea7-4a49-9746-824e32131203

Firefox 28.0a1 Crash Report [@ xpc::PrincipalImmuneToScriptPolicy ]

Comment 3

[Loic]

Do you have simple STR (step by step) with a fresh profile and only Firebug?

Comment 4

[Lars Gusowski [:lagu]]

I had the crash today to :(

https://crash-stats.mozilla.com/report/index/48976be1-c1cf-4152-8027-5b7a82131209

Comment 5

[Lars Gusowski [:lagu]]

and again 
https://crash-stats.mozilla.com/report/index/b8bfa0a4-3e56-402a-ae65-b0a722131209

But still no STR

Comment 6

[Petruta Horea [:phorea], Desktop QA]

Mozilla/5.0 (Windows NT 6.3; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0

I had no crashes using latest Aurora (20131211004000) with Firebug and steps from Comment 0.

Comment 7

[u279076]

Hi Ashish, we have been unable to reproduce this on our end. Can you please provide reliable steps to reproduce?

Comment 8

[u279076]

This has risen significantly in the last several days to #8 @ 1.48% on Aurora and now qualifies as a topcrash. Though it's very low volume on Nightly with only 3 crashes reported. We really need to find reliable steps to reproduce and a regression range.

Comment 9

[u279076]

One comment mentions JSBin, maybe that in conjunction with Firebug is a way to go.

Ioana, please have someone on your team look for steps to reproduce ASAP.

Comment 10

[Ioana (away)]

Cornel, please try to help out here - see comment 9.

Comment 11

[Cornel Ionce [:noni] [Hubs QA]]

I was unable to reproduce this using latest Nightly, latest Aurora and 2014-01-09 Aurora build (most affected version accordingly to the crash-report graph) on Windows 7x32 (68.10% of the crashes).
Tried with the 2014-01-09 BR and HU locales also, where several crashes occurred.


Installed addons: 
- Firebug 1.12.5
- Test Pilot 1.2.3
- Thumbnail Zoom Plus 2.7

Not reproduced using the STR from the description and exploratory testing around them.

Ashish, could you please provide more details steps for this or maybe a video of the crash occurring?

Comment 12

[Ashish Namdev]

Hi ,

I tried with Firefox 26.0 , it's not reproduced

i don't have nightly installed as of now , will prepare my system with nightly and update you
by tomorrow EOD

Comment 13

[Lukas Blakk [:lsblakk] use ?needinfo]

Ashish, 28 is Aurora now so you'll want to try and reproduce with the latest build from http://www.mozilla.org/en-US/firefox/channel/#aurora

Re-nominate for tracking if this is reproducible.

Comment 14

[Ashish Namdev]

I am in limited network connectivity , could not try :( , sorry for inconvenience caused .

Thanks Lukas for suggestion , i will try on Aurora 28 and will update .

Keeping needinfo flag alive until i test on Aurora 28

Comment 15

[Ashish Namdev]

Hi ,

Tried to reproduce this bug on Nightly 29.0a1 (2014-01-30).

Issue is not reproducible on latest Nightly Build.

Comment 16

[u279076]

(In reply to Ashish Namdev from comment #15)
> Hi ,
> 
> Tried to reproduce this bug on Nightly 29.0a1 (2014-01-30).

Hi Ashish, this bug was never known to affect Firefox 29. Can you please retest with the latest Aurora? You can get it from http://aurora.mozilla.org

Comment 17

[Bobby Holley (:bholley)]

This is a dupe of bug 941707 and bug 911400 I think.

Comment 18

[u279076]

Assuming fixed based on crash-stats, this shows up nowhere in any of the branches top-300 reports.

Comment 19

[Joshua Mitchell (Inactive)]

Issue is resolved - clearing old keywords - qa-wanted clean-up