1212858 - Cannot load content in Safe Mode because OMTC is disabled

Status: RESOLVED DUPLICATE of bug 1187322

(Core :: Graphics, defect)

Description

[beingalink]

Attachment: Screenshot 2015-10-08 15.59.45.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20151008030232

Steps to reproduce:

Open Firefox in normal Mode.
In the Burger Menu click "? (Help)" --> Restart with Add-ons Disabled
Confirm


Actual results:

Firefox starts in Safe Mode but no Content gets displayed. The content seems to get loaded though since the spinners on the tabs work as if everything was normal. In the content section there is only a spinner in front of grey background (see screenshot attached to this bug)


Expected results:

Content should display normally in safe mode.

Comment 1

[Markus Stange [:mstange]]

I can confirm. It looks like safe mode disables OMTC again, and without OMTC we can't display anything from the content process.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

I can't reproduce this on Windows or Linux. Looks like we'll need someone to bisect on a Mac.

Comment 3

[u279076]

I can reproduce this in today's Nightly build -- working now on finding the regression window.

Comment 4

[u279076]

It looks like this was caused by bug bug 1179051 (cc dvander).

Pushlog:
> https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=15155971639c&tochange=9c919ce631ea
> https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e673cc171604a05f6d1cde745b5d7c61074be342&tochange=08508716085a41245854b88d5e1f13b315a5ab4f

[Tracking Requested - why for this release]: Mac OS users running in safe mode will not be able to render any web content. This should probably block release of Firefox 42 given that running in safe mode is a common troubleshooting step.

Comment 5

[David Anderson [:dvander] - inactive, e-mail if emergency]

Markus, around when bug 1179051 landed we had turned off BasicCompositor on Mac. Did we reverse that decision?

(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #4)
> It looks like this was caused by bug bug 1179051 (cc dvander).
> 
> Pushlog:
> > https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=15155971639c&tochange=9c919ce631ea
> > https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e673cc171604a05f6d1cde745b5d7c61074be342&tochange=08508716085a41245854b88d5e1f13b315a5ab4f
> 
> [Tracking Requested - why for this release]: Mac OS users running in safe
> mode will not be able to render any web content. This should probably block
> release of Firefox 42 given that running in safe mode is a common
> troubleshooting step.

Can you actually reproduce this on 42? I would think this is E10S only.

Comment 6

[u279076]

(In reply to David Anderson [:dvander] from comment #5)
> Can you actually reproduce this on 42? I would think this is E10S only.

You are correct. This reproduces in Firefox 42 builds where e10s is enabled (ie. Nightly) but not where it is disabled (ie. Beta). Therefore I reverse my red-flag for blocking release, definitely should block e10s though.

Comment 8

[Tracy Walker [:tracy]]

clearing NI to get back into triage.  Should be an m8+ because of useless Safe Mode.