1026521 - e10s blank page with hardware acceleration disabled

Status: RESOLVED FIXED

(Core :: General, defect, P2)

Description

[iamjayakumars]

Hi, When i run the e10s in Safemode, it shows the blank page for all the website. 

System info: 
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140617030203 CSet: bb35d1b73634

Comment 1

[Mike Conley (:mconley) (:⚙️)]

cpeterson - didn't you report something similar yesterday when we were debugging bug 1002354?

Comment 2

[Chris Peterson [:cpeterson]]

I filed bug 1026093 about the safemode blank pages and Flash crash. It might be a good idea to track separate bugs for the blank pages and Flash crashes.

Comment 3

[Chris Peterson [:cpeterson]]

Moving old M2 P2 bugs to M4.

Comment 4

[Chris Peterson [:cpeterson]]

Move old M2's low-priority bugs to M6 milestone.

Comment 5

[Chris Peterson [:cpeterson]]

oops: old M2 P2 bugs should have been moved to new M4 milestone, not M6.

Comment 6

[Andrew McCreight [:mccr8]]

I see this same behavior with hardware acceleration disabled, so it is a broader problem than just safe mode.  I think safe mode disables hardware acceleration.

Comment 7

[Chris Peterson [:cpeterson]]

If this problem happens when hardware acceleration is disabled outside of safe mode, then we should fix this sooner than M4.

Comment 8

[Andrew McCreight [:mccr8]]

Yeah, I can reproduce this on my other OSX machine by disabling hardware acceleration in preferences.  I couldn't reproduce the crashing with a little bit of experimenting, but maybe that's because no page was actually fully loading. ;)

Comment 11

[:Gijs (out for now; he/him)]

(In reply to Chris Peterson (:cpeterson) from comment #7)
> If this problem happens when hardware acceleration is disabled outside of
> safe mode, then we should fix this sooner than M4.

Yes, it does. I'm confused because other bugs say that e10s is "disabled" when hwa is off, which isn't really what happens IME: I just get no web content (about: pages load if they're the first thing in the tab, but if you try to load http://www.example.com and then an about: page, that just infinite-spins at you). But all the tab titles are underlined, so e10s is still on.

Can we make hwa being off either not break rendering, or turn off e10s properly? The current state is not usable.

Comment 12

[Jim Mathies [:jimm]]

(In reply to :Gijs Kruitbosch from comment #11)
> (In reply to Chris Peterson (:cpeterson) from comment #7)
> > If this problem happens when hardware acceleration is disabled outside of
> > safe mode, then we should fix this sooner than M4.
> 
> Yes, it does. I'm confused because other bugs say that e10s is "disabled"
> when hwa is off, which isn't really what happens IME: I just get no web
> content (about: pages load if they're the first thing in the tab, but if you
> try to load http://www.example.com and then an about: page, that just
> infinite-spins at you). But all the tab titles are underlined, so e10s is
> still on.
> 
> Can we make hwa being off either not break rendering, or turn off e10s
> properly? The current state is not usable.

Did you disable ForceRTL? That has known compat issues with e10s.

Comment 13

[:Gijs (out for now; he/him)]

(In reply to Jim Mathies [:jimm] from comment #12)
> (In reply to :Gijs Kruitbosch from comment #11)
> > (In reply to Chris Peterson (:cpeterson) from comment #7)
> > > If this problem happens when hardware acceleration is disabled outside of
> > > safe mode, then we should fix this sooner than M4.
> > 
> > Yes, it does. I'm confused because other bugs say that e10s is "disabled"
> > when hwa is off, which isn't really what happens IME: I just get no web
> > content (about: pages load if they're the first thing in the tab, but if you
> > try to load http://www.example.com and then an about: page, that just
> > infinite-spins at you). But all the tab titles are underlined, so e10s is
> > still on.
> > 
> > Can we make hwa being off either not break rendering, or turn off e10s
> > properly? The current state is not usable.
> 
> Did you disable ForceRTL? That has known compat issues with e10s.

Yes, otherwise it would have crashed on startup...

Comment 14

[Dave Townsend [:mossop]]

(In reply to :Gijs Kruitbosch from comment #11)
> (In reply to Chris Peterson (:cpeterson) from comment #7)
> > If this problem happens when hardware acceleration is disabled outside of
> > safe mode, then we should fix this sooner than M4.
> 
> Yes, it does. I'm confused because other bugs say that e10s is "disabled"
> when hwa is off, which isn't really what happens IME: I just get no web
> content (about: pages load if they're the first thing in the tab, but if you
> try to load http://www.example.com and then an about: page, that just
> infinite-spins at you). But all the tab titles are underlined, so e10s is
> still on.
> 
> Can we make hwa being off either not break rendering, or turn off e10s
> properly? The current state is not usable.

Yeah this is not right, we have code in place that is meant to block e10s for hardware acceleration being disabled: http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.cpp#4616

Comment 15

[:Gijs (out for now; he/him)]

(In reply to Dave Townsend [:mossop] from comment #14)
> (In reply to :Gijs Kruitbosch from comment #11)
> > (In reply to Chris Peterson (:cpeterson) from comment #7)
> > > If this problem happens when hardware acceleration is disabled outside of
> > > safe mode, then we should fix this sooner than M4.
> > 
> > Yes, it does. I'm confused because other bugs say that e10s is "disabled"
> > when hwa is off, which isn't really what happens IME: I just get no web
> > content (about: pages load if they're the first thing in the tab, but if you
> > try to load http://www.example.com and then an about: page, that just
> > infinite-spins at you). But all the tab titles are underlined, so e10s is
> > still on.
> > 
> > Can we make hwa being off either not break rendering, or turn off e10s
> > properly? The current state is not usable.
> 
> Yeah this is not right, we have code in place that is meant to block e10s
> for hardware acceleration being disabled:
> http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.
> cpp#4616

Yeah, too bad the pref getter there gets overridden on OS X straight away, unless you're on a really old version of OS X:

http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/nsCocoaFeatures.mm#152

Comment 16

[Dave Townsend [:mossop]]

(In reply to :Gijs Kruitbosch from comment #15)
> (In reply to Dave Townsend [:mossop] from comment #14)
> > (In reply to :Gijs Kruitbosch from comment #11)
> > > (In reply to Chris Peterson (:cpeterson) from comment #7)
> > > > If this problem happens when hardware acceleration is disabled outside of
> > > > safe mode, then we should fix this sooner than M4.
> > > 
> > > Yes, it does. I'm confused because other bugs say that e10s is "disabled"
> > > when hwa is off, which isn't really what happens IME: I just get no web
> > > content (about: pages load if they're the first thing in the tab, but if you
> > > try to load http://www.example.com and then an about: page, that just
> > > infinite-spins at you). But all the tab titles are underlined, so e10s is
> > > still on.
> > > 
> > > Can we make hwa being off either not break rendering, or turn off e10s
> > > properly? The current state is not usable.
> > 
> > Yeah this is not right, we have code in place that is meant to block e10s
> > for hardware acceleration being disabled:
> > http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.
> > cpp#4616
> 
> Yeah, too bad the pref getter there gets overridden on OS X straight away,
> unless you're on a really old version of OS X:
> 
> http://mxr.mozilla.org/mozilla-central/source/widget/cocoa/nsCocoaFeatures.
> mm#152

Ugh yeah, there should be an && in there

Comment 17

[Dave Townsend [:mossop]]

I filed bug 1095559 to properly disable e10s with HW acceleration.

Comment 18

[James Willcox (:snorp) ([e-mail]) (he/him)]

So this bug should be fixed now that 1095559 landed?

Comment 19

[Dave Townsend [:mossop]]

Yes!