Closed Bug 1257575 Opened 6 years ago Closed 5 years ago

[e10s] Black/White artifacting when maximizing the Hello window

Categories

(Core :: Graphics, defect)

All
Windows
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
e10s + ---

People

(Reporter: cmuresan, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

[Affected versions]:
Latest Nightly 48.0a1, Build ID 20160316030233

[Affected platforms]:
- Windows 7 x32, 10 x64

[Prerequisites]:
- Set loop.remote.autostart to true in about:config
- Add the Hello feature to the Menu (if not already added) from customization menu.

[Steps to reproduce]:
1. Open the browser and visit any website.
2. Click the Hello button and after the dropdown is displayed, click "Browse this page with a friend"
3. Minimize and maximize the Hello window repeatedly. (at least 10 times)
4. Observe the Hello window's behavior.

[Expected result]:
- The window is minimised and maximised without any rendering issues.

[Actual result]:
- While maximizing, some odd artifacting can be observed on the Hello window for short periods of time (~1 sec).

[Notes]:
- Sometimes the artifacts are black, sometimes white.
Blocks: loop-e10s
Does disabling hardware acceleration have any affect on the artifacting?
Flags: needinfo?(ciprian.muresan)
I retested the issue on Latest Nightly 48.0a1, Build ID 20160327030437, Hello version 1.2.2 and the artifacting is less frequent and mostly transparent or white. Disabling hardware acceleration does not change this behavior.
Flags: needinfo?(ciprian.muresan)
Jim: can you propose a component for this?  This doesn't feel like a bug the Hello team can fix.
Flags: needinfo?(jmathies)
feels like Graphics or layout related. Milan, does this sound like it's related to something your team has open?
Flags: needinfo?(jmathies) → needinfo?(milan)
Does it behave any differently (better or worse) if you set environment variable MOZ_DISABLE_FORCE_PRESENT to 1 and run the test?
Flags: needinfo?(milan) → needinfo?(ciprian.muresan)
Whiteboard: [gfx-noted]
Attached image SSoftheissue.png
I've manually added "MOZ_DISABLE_FORCE_PRESENT" in about:config. The artifacting is less noticeable, but still present. I've added a SSoftheissue.png to show this.
Flags: needinfo?(ciprian.muresan)
It wouldn't be about:config, that shouldn't make a difference.  It needs to be in the Windows system environment variables instead.
(In reply to Milan Sreckovic [:milan] from comment #7)
> It wouldn't be about:config, that shouldn't make a difference.  It needs to
> be in the Windows system environment variables instead.
Flags: needinfo?(ciprian.muresan)
I observed no difference after I set up the system variable.
Flags: needinfo?(ciprian.muresan)
Moving to Core -> Graphics for now.
Component: Client → Graphics
Product: Hello (Loop) → Core
(In reply to Ciprian Muresan [:cmuresan] from comment #9)
> I observed no difference after I set up the system variable.

That suggests this problem isn't a result of the patch from bug 1232042
(In reply to Mark Banner (:standard8) from comment #10)
> Moving to Core -> Graphics for now.

Possibly graphics, but the fact that it doesn't change when hardware acceleration is off makes me question it somewhat.

Did this ever work properly?  As in, can we find a regression range?
(In reply to Milan Sreckovic [:milan] from comment #12)
> Did this ever work properly?  As in, can we find a regression range?

Ciprian, can you please answer these questions?
Flags: needinfo?(ciprian.muresan)
It seems to have been the same since the Hello add-on was implemented. Went as far back as a build from 03.15.2016 and the artifacting is still there.
Flags: needinfo?(ciprian.muresan)
Based on comment 14 this is not a regression.
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.