1153843 - Issue on Mac after updating Yosemite

Status: RESOLVED DUPLICATE of bug 1151644

(Core :: Widget: Cocoa, defect)

Description

[Armen [:armenzg]]

Attachment: IMG_20150413_091932.jpg

Nightly is looking like this.
Beta is still working.
I'm on 10.10.3 on a 3-year old Mac Air.

Comment 1

[Armen [:armenzg]]

Attachment: output2.txt

I run the latest m-c Debug build against the same profile.

./NightlyDebug.app/Contents/MacOS/firefox -p default &> ~/Desktop/output.txt

I can't tell what is going on.

Comment 2

[Steven Michaud [:smichaud] (Retired)]

So ... the page's content is entirely blank?

Though your screenshot is more easily decipherable than most, I really hate it when people post a screenshot of a problem with minimal or no description.

Which nightly?  Today's mozilla-central nightly?

Does this happen with a clean profile?

Have you been using multiple Firefox branches with the same profile?

The following, from your debug log, may be significant.  But because our debug builds' logs are so very noisy, it's difficult to tell.

[1308] WARNING: Enabling vsync compositor
: file /builds/slave/m-cen-m64-d-000000000000000000/build/src/gfx/layers/ipc/CompositorParent.cpp, line 483
[1308] WARNING: Failed to initialise Compositor: file /builds/slave/m-cen-m64-d-000000000000000000/build/src/gfx/layers/ipc/CompositorParent.cpp, line 1305
[1308] WARNING: Failed to create an OMT compositor.: file /builds/slave/m-cen-m64-d-000000000000000000/build/src/widget/nsBaseWidget.cpp, line 1165

Comment 3

[Armen [:armenzg]]

(In reply to Steven Michaud from comment #2)
> So ... the page's content is entirely blank?
> 
Yes. Even though I know that the tabs have been loaded. I can drag

> Though your screenshot is more easily decipherable than most, I really hate
> it when people post a screenshot of a problem with minimal or no description.
> 
I hate reporting bugs because I never remember everything that everyone expects for a proper report.

> Which nightly?  Today's mozilla-central nightly?
> 
It is from m-c. I know it is version 40.

> Does this happen with a clean profile?
> 
No, it does not.

> Have you been using multiple Firefox branches with the same profile?
> 
Yes

> The following, from your debug log, may be significant.  But because our
> debug builds' logs are so very noisy, it's difficult to tell.
> 
> [1308] WARNING: Enabling vsync compositor
> : file
> /builds/slave/m-cen-m64-d-000000000000000000/build/src/gfx/layers/ipc/
> CompositorParent.cpp, line 483
> [1308] WARNING: Failed to initialise Compositor: file
> /builds/slave/m-cen-m64-d-000000000000000000/build/src/gfx/layers/ipc/
> CompositorParent.cpp, line 1305
> [1308] WARNING: Failed to create an OMT compositor.: file
> /builds/slave/m-cen-m64-d-000000000000000000/build/src/widget/nsBaseWidget.
> cpp, line 1165

Comment 4

[Armen [:armenzg]]

Thank you for promptly replying to this bug.

Comment 5

[Steven Michaud [:smichaud] (Retired)]

> So ... the page's content is entirely blank?

And also the two menubars (containing the tabs and the location bar).

It looks like the browser window is maximized but not in fullscreen mode.  Is that correct?

(I really do need to install OS X 10.10.3 somewhere.  It seems to be full of bugs.)

Comment 6

[Steven Michaud [:smichaud] (Retired)]

>> Though your screenshot is more easily decipherable than most, I
>> really hate it when people post a screenshot of a problem with >
>> minimal or no description.
>
> I hate reporting bugs because I never remember everything that
> everyone expects for a proper report.

All you need to do is tell me what's in front of your eyes :-)

It's surprising how many people can't do that.

Comment 7

[Steven Michaud [:smichaud] (Retired)]

(Following up comment #6)

> All you need to do is tell me what's in front of your eyes :-)

There's a bit more to it than that, it's true.  It usually helps if you also describe what you were trying to do -- the steps that led up to the problem (which may or may not be reproducible).  Even better if you try those steps a few times and find out whether or not they're reproducible.

Just think what would happen if you emailed a picture of your car to a car repair shop under the subject line "it's broken" :-)

Comment 8

[Armen [:armenzg]]

(In reply to Steven Michaud from comment #6)
> >> Though your screenshot is more easily decipherable than most, I
> >> really hate it when people post a screenshot of a problem with >
> >> minimal or no description.
> >
> > I hate reporting bugs because I never remember everything that
> > everyone expects for a proper report.
> 
> All you need to do is tell me what's in front of your eyes :-)
> 
> It's surprising how many people can't do that.

Please be respectful. We should not be talking like this anywhere.

STR:
* Update to Yosemite 10.10.3
* Start the browser

Expected results:
* Tabs and menu bars from previous session are restored

Actual results:
* Tabs and menu bars from previous session are *not* restored

It is not running on full screen.
Using a clean profile works.

Comment 9

[Steven Michaud [:smichaud] (Retired)]

> Please be respectful. We should not be talking like this anywhere.

I frankly *am* being quite respectful.

And incomplete bug reports are a serious problem.  You waste my time (and that of whoever else reads this bug report) by making me ask questions that should be answered in *any* bug report.  We have a document somewhere that tells "new users" what kinds of questions need to be answered ... but you're not a "new user".

I realize that you're probably very busy doing something else when you see a bug, and that having to open a bug report is a serious disruption.  The same thing happens to me.  But things would go a lot more smoothly if every Mozilla person, at least, gave this same minimal information in every bug report.

Comment 10

[Armen [:armenzg]]

You're right. I'm sorry.

Can you please let me know if there is anything else lacking?

I assume I could rename my profiles to remind me which version to use with each one.
I assuming that this is due to using multiple gecko versions with one profile, we could perhaps add a prompt when trying to use gecko version different than what it was used when creating that profile?

Comment 11

[Steven Michaud [:smichaud] (Retired)]

Using the same profile for multiple Firefox branches has always been somewhat risky.  It's always been true that it can lead to some kind of "profile corruption" -- weird behavior that's otherwise inexplicable.  But things have gotten much worse recently, since bug 1112702 landed on the trunk, which makes large changes in how profile information is updated (https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/3IqDew1O-Vk).

I got away with using the same profile for many years, without any serious problems.  Now I use the Profile Manager and create two additional vanilla testing profiles, one called "vanilla" for m-c and aurora nightlies, and one called "release" for everything else.  Bug 1112702 sometimes causes my "vanilla" profile (or parts of it) to spontaneously reset.  But both my "vanilla" and "release" profiles are so simple that it's easy to periodically throw them away and re-create them.

Comment 12

[Steven Michaud [:smichaud] (Retired)]

Actually the Developer Edition (aka the aurora branch) creates it's own profile by default, so you don't need to worry about it.

Comment 13

[Steven Michaud [:smichaud] (Retired)]

I won't be getting back to this bug until I can install OS X 10.10.3 somewhere.  When I do, I'll let you know if I have any more questions.  The basic ones have (I think) already been answered.

Comment 14

[Stefan [:stefanh]]

Attachment: Blank_window.png

I see this too, or at least something similar: this is with the latest nightly on 10.9.5. This is with an old Mac mini with Intel HD Graphics 3000.

Comment 15

[Stefan [:stefanh]]

OK, so this looks related to the profile. I don't see this with a new profile. Console output differs also (just guessing this is the relevant parts):

With a clean profile:
[67296] WARNING: Enabling vsync refresh driver
: file /Users/stefan/Moz/comm-central/mozilla/layout/base/nsRefreshDriver.cpp, line 862
[67296] WARNING: Enabling vsync compositor
: file /Users/stefan/Moz/comm-central/mozilla/gfx/layers/ipc/CompositorParent.cpp, line 483

With an old profile
[67315] WARNING: Enabling vsync compositor
: file /Users/stefan/Moz/comm-central/mozilla/gfx/layers/ipc/CompositorParent.cpp, line 483
[67315] WARNING: Failed to initialise Compositor: file /Users/stefan/Moz/comm-central/mozilla/gfx/layers/ipc/CompositorParent.cpp, line 1305
[67315] WARNING: Failed to create an OMT compositor.: file /Users/stefan/Moz/comm-central/mozilla/widget/nsBaseWidget.cpp, line 1165

This is the Graphics part from about:support when running the old profile
Asynchronous Pan/Zoom	none
Device ID	0x 126
GPU Accelerated Windows	1/1 OpenGL (OMTC)
Vendor ID	0x8086
WebGL Renderer	Intel Inc. -- Intel HD Graphics 3000 OpenGL Engine
windowLayerManagerRemote	true
AzureCanvasBackend	skia
AzureContentBackend	quartz
AzureFallbackCanvasBackend	none
AzureSkiaAccelerated	0

I guess it's some setting that differs, but I'm unable to figure out what it is.

Comment 16

[Stefan [:stefanh]]

I figured it out: setting "layers.acceleration.disabled" to true will give me a blank window (my regular profile had this). Steven says he see it too.

Comment 17

[Stefan [:stefanh]]

Armen, can you also reproduce/not reproduce by flipping the "layers.acceleration.disabled" pref in about:config?

Comment 18

[Armen [:armenzg]]

Steps taken:
* Opened Firefox beta and default profile
* about:config and set layers.acceleration.disabled to false
* Closed Firefox Beta
* Opened Nightly
* It works as expected

Is layers.acceleration.disabled==True the default?
Do we have metrics on how many people have it disabled?
It seems that we could have a lot of users get into trouble if they upgrade Yosemite.
Is there any unit test that could catch this?

Comment 19

[Stefan [:stefanh]]

Appears that this is already known - bug 1151644.

Comment 20

[Steven Michaud [:smichaud] (Retired)]

Thanks for figuring this out, Stefan!  You saved me a lot of time.