1138437 - e10s tab crashes every time

Status: RESOLVED INVALID

(Core :: XPCOM, defect)

Description

[u52928]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150301030224

Steps to reproduce:

Clicked File -> New e10s Window


Actual results:

Tab crashed

https://crash-stats.mozilla.com/report/index/0cb9a593-5c40-49bb-ba81-285762150301
and
https://crash-stats.mozilla.com/report/list?signature=mozalloc_abort%28char+const*+const%29+|+NS_DebugBreak+|+Initialize%28%29&product=Firefox&query_type=contains&range_unit=weeks&process_type=any&hang_type=any&date=2015-03-01+20%3A00%3A00&range_value=1#reports


Expected results:

I should have been able to continue.

Comment 1

[Andrew McCreight [:mccr8]]

It looks like somebody implemented nsIURI using a JS component, and one is created during startup, in XPConnect initialization, which causes XPCOM to reenter and crash.

Does this happen in safe mode?  I'm guessing some extension you have installed is causing this.  It would be good to figure out which one.

Comment 2

[Andrew McCreight [:mccr8]]

about:support has the list of extensions, if you want to paste that list here.  Or you could try isolating the extension yourself by disabling some.

Comment 3

[u52928]

Thanks. I don't have much time ... sorry.

Here are my extensions.
Adblock Edge 2.1.8
Beef Taco (Targeted Advertising Cookie Opt-Out) 1.3.7
BetterPrivacy 1.68
Classic Theme Restorer 1.2.9.6
Cleanest Addon Manager 7.0
Custom Toolbar Buttons 0.6.0.8
Download Status Bar 12.3.0
Download YouTube Videos as MP4 1.7.31
DownThemAll! 2.0.18
FindBar Tweak 1.4.18
FireFTP 2.0.22
Flashblock 1.5.18
FoxyProxy Standard 4.5.1 [DISABLED]
GitHub Extension Installer 1.5.0 [DISABLED]
GlobalFindBar 1.0
Google Privacy 0.2.4
Google search link fix 1.4.9
google-no-tracking-url 1.3.1
Greasemonkey 2.3
ImageTweak 0.25.1
JS Switch 0.2.10
keyconfig 20110522
Nightly Tester Tools 3.7
NO Google Analytics 0.6
NoScript 2.6.9.16
Open link in... 1.9
Permit Cookies 2 1.0.1
Print Edit 14.2
Quick Locale Switcher 1.7.8.5
QuickPageZoom 1.6.3
Remove It Permanently 1.0.6.10
Restart 1.2.3
SaveAsFilename 0.1
Screengrab  (fix version) 0.98.05c
Site Favicon in Urlbar 8.1
SmoothWheel (AMO) 0.45.8.20130519.3
Status-4-Evar 2015.02.06.23
Theme Font & Size Changer 35.4
Throbber Restored 1.4
UAControl 0.1.3.1
User-Agent JS Fixer 1.3
YouTube Unblocker 0.6.8 [DISABLED]

Comment 4

[Boris Zbarsky [:bzbarsky]]

> It looks like somebody implemented nsIURI using a JS component

Note that in general we do claim to support that.

Comment 5

[u52928]

I'm not sure what you mean.

Comment 6

[Andrew McCreight [:mccr8]]

(In reply to JoeG from comment #5)
> I'm not sure what you mean.

We're just discussing a possible underlying cause of your crash.  Nothing you need to worry about in particular. :)

Comment 7

[u52928]

Heh-heh, whoops. Thanks

Comment 8

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I did a search of add-ons that implement custom protocol handlers and compared it to the list here (on Andrew's suggestion). Here are the common add-ons.

Custom Toolbar Buttons 0.6.0.8
FireFTP 2.0.22
Nightly Tester Tools 3.7

Could you try disabling these add-ons and see if the crash is fixed? If we can find out which add-on is causing the problem, it will be much easier to fix it.

Comment 9

[Andrew McCreight [:mccr8]]

I tried installing FireFTP 2.0.22 and Nightly Tester Tools 3.7, but it seemed to be okay.  I couldn't find Custom Toolbar Buttons 0.6.0.8, which may mean that it is known to be out of date, and thus doesn't show up in the default search.

Comment 10

[u52928]

Thanks for your input.

I disabled Custom Toolbar Buttons 0.6.0.8, which is indeed an out-dated extension, but the e10s tab crashed anyway.
https://crash-stats.mozilla.com/report/index/2debcb93-e248-4eff-93ad-a13d52150303
https://crash-stats.mozilla.com/report/index/cfad9eee-332f-4673-ba41-a77db2150303

Then I tried with a brand-new profile. When Fx started, I was told I'm helping to test e10s. What happened next was really weird: There was no crash, but no matter what website I tried to visit, all I got was a blank, white window! The address was in the address bar, but no website appeared. When I clicked to open a new tab, one opened, but when I typed in an address (e.g. "bbc.com"), it was the same; nothing whatsoever appeared in the window. It was white.

Could it have something to do with my Matrox 9028 graphics card? Awhile back (unrelated to e10s) there was an issue with the Matrox drivers not being supported due to something or other.

Anyway, sorry folks, but this is over my head.

Comment 11

[Andrew McCreight [:mccr8]]

(In reply to JoeG from comment #10)
> I disabled Custom Toolbar Buttons 0.6.0.8, which is indeed an out-dated
> extension, but the e10s tab crashed anyway.

Thanks for trying it.

> Could it have something to do with my Matrox 9028 graphics card? Awhile back
> (unrelated to e10s) there was an issue with the Matrox drivers not being
> supported due to something or other.

Yeah, that's what happens when you try to enable e10s with hardware acceleration disabled.  It is supposed to detect that and not enable e10s, but I guess it isn't working for you for some reason.  That's what you'd end up with if you didn't crash when you opened a new window in e10s mode.

Comment 12

[Bryan Price]

I had one extension enabled.  NoScript.  Which I could have sworn was in the Wiki as being e10s compatible.  Although I see it isn't, not now.  I'm reporting that bug, too.  I'm turning e10s off, and forgetting about e10s until Mozilla decides to turn it back on for me.  Again.

https://crash-stats.mozilla.com/report/index/bp-efde21c3-0310-46a7-bcd6-97aca2150524

Build 20150524030234, 64-bit Win.