574631 - [D2D] Page Content and Chrome Flickering with D2D Enabled

Status: RESOLVED DUPLICATE of bug 574599

(Core :: Graphics, defect)

Description

[Ryan Jones-Ward [:sciguyryan]]

The builds after http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1277431020/ are unusable due to the content and chrome flickering when the page is loading.

I haven't tracked down a regression range but the last bug change was this Bug 513162. If anyone has a regression range please post it here.

Comment 1

[Oskar Ivanić (:icecold)]

Confirmed. Page goes black and it turn to normal all the time.

Comment 2

[Ryan Jones-Ward [:sciguyryan]]

(In reply to comment #1)
> Confirmed. Page goes black and it turn to normal all the time.

Yes. That's exactly what happens here.

Comment 3

[Gary [:streetwolf52]]

Confirmed. 

Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:1.9.3a6pre) Gecko/20100623 Minefield/3.7a6pre - Build ID: 20100624140418

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

Is this only with D2D enabled? Is that enabled by default?

Comment 6

[Josh Tumath]

(In reply to comment #5)
> Is this only with D2D enabled? Is that enabled by default?
No. I don't think it will be for a while.

Comment 7

[Bill Gianopoulos [:WG9s]]

(In reply to comment #5)
> Is this only with D2D enabled? Is that enabled by default?

This is only with D2D and it is not enabled by default, so I am not at all sure critical is the correct severity.  Actually, I could make a better case for it being blocker severity as it kind of really puts a halt to testing D2D than I could for critical.

This should probably not be a blocker for 1.9.3 either, but should probably instead block the bug to enable D2D by default.

Comment 8

[Ryan Jones-Ward [:sciguyryan]]

It's pretty critical since a lot of nightly testers are using D2D for testing also. That is the whole point of software testers after all - if nobody is able to test it, the feature will never get work correctly.

Comment 9

[Gary [:streetwolf52]]

No Problems:  522df66198cf

Big Problems: 51bd519736c4

Comment 10

[Ryan Jones-Ward [:sciguyryan]]

Seems pretty certain that it is a regression from Bug 513162 then.

Comment 11

[Bas Schouten (:bas.schouten)]

(In reply to comment #6)
> (In reply to comment #5)
> > Is this only with D2D enabled? Is that enabled by default?
> No. I don't think it will be for a while.

Actually, it will be pretty soon.

Comment 12

[Bas Schouten (:bas.schouten)]

(In reply to comment #7)
> (In reply to comment #5)
> > Is this only with D2D enabled? Is that enabled by default?
> 
> This is only with D2D and it is not enabled by default, so I am not at all sure
> critical is the correct severity.  Actually, I could make a better case for it
> being blocker severity as it kind of really puts a halt to testing D2D than I
> could for critical.
> 
> This should probably not be a blocker for 1.9.3 either, but should probably
> instead block the bug to enable D2D by default.
It is pretty bad, because we're planning to enable D2D by default on all DX10 hardware before the end of the quarter.

Comment 14

[Ryan A. C.]

I'm not entirely certain but it also looks like cleartype isn't functioning on the flickering content - could be related to Bug 568495

Comment 15

[Bill Gianopoulos [:WG9s]]

(In reply to comment #10)
> Seems pretty certain that it is a regression from Bug 513162 then.

I verified it is definitely 513162 using hg bisect.

Comment 16

[Bill Gianopoulos [:WG9s]]

This begs up the question.  Should there be a windows test box running with d2d enabled? And would that even really make sense given that we are really not looking at what is displayed, I have no idea if it would have even caught this.

Comment 17

[Bill Gianopoulos [:WG9s]]

(In reply to comment #12)
> (In reply to comment #7)
> > (In reply to comment #5)
> > > Is this only with D2D enabled? Is that enabled by default?
> > 
> > This is only with D2D and it is not enabled by default, so I am not at all sure
> > critical is the correct severity.  Actually, I could make a better case for it
> > being blocker severity as it kind of really puts a halt to testing D2D than I
> > could for critical.
> > 
> > This should probably not be a blocker for 1.9.3 either, but should probably
> > instead block the bug to enable D2D by default.
> It is pretty bad, because we're planning to enable D2D by default on all DX10
> hardware before the end of the quarter.

I was not trying to say it was not bad.  Just that given that it is not enabled by default, critical is not really justified, but that given that it blocks development of D2D blocker,which is actually a higher severity IS jsutified.

->> BLOCKER

Comment 18

[Bas Schouten (:bas.schouten)]

(In reply to comment #16)
> This begs up the question.  Should there be a windows test box running with d2d
> enabled? And would that even really make sense given that we are really not
> looking at what is displayed, I have no idea if it would have even caught this.

It's all being worked on! And it's actually even a blocker for enabling D2D by default, so hopefully we'll have it soon! Bug 549120

Comment 19

[Oskar Ivanić (:icecold)]

Bas, can this be fixed by next nightly? (626 build) I'm asking this because we're cut off from Direct2D by this bug.