1580107 - Moonlight client freezes when host views full screen video since recent version

Status: NEW

(Core :: Graphics, defect, P3)

Description

[limeclipse]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Connect with moonlight to a host PC. Open any video or streaming service (either as client or host) and go full screen.

Actual results:

The moonlight client freezes up until full screen mode is exited.

This has been the case since recent versions (I'd say no longer than 1.5 months ago). This does not happen in Chromium based browsers.

Expected results:

Video should be visible on the moonlight client.

Comment 1

[Daniel Bodea [:danibodea]]

In order to confirm your issue, I need to reproduce it. Please provide some more detailed steps to reproduce.

1. How do I connect with Moonlight to a host PC?
2. What kind of video or streaming service should I open?
3. Which exact version of Firefox are you currently using? (the one where the issue reproduces. Is it Beta channel?)
4. Can you record your screen while reproducing the issue?

Thank you for your contribution!

Comment 2

[limeclipse]

How do I connect with Moonlight to a host PC?
You need a computer with a Nvidia graphics card and Nvidia Experience installed. In Nvidia Experience, you can turn on Nvidia Shield. When Shield is turned on, Moonlight should see the host computer on the local network immediately. You can also add a remote IP address for remote computers. It has a typical PIN code authorization method when you connect for the first time.

What kind of video or streaming service should I open?
Any webpage that has a (html5) video player with the option to go full-screen. E.g. Youtube, Twitch.

As for the other two questions, I'll have to get back to that when I get home. So far have only tried the mainstream version (non beta/developer editions) but the issue has been present for quite a few updates already. I could record my screen reproducing the issue but it literally just freezes the video on the frame it went full-screen and resumes when full-screen is exited.

Comment 3

[Daniel Bodea [:danibodea]]

We can't attempt reproduction here so I will set the component as (Core) Graphics and let the devs have a more appropriate opinion on this.
Reporter, please attempt to reproduce it while is safe mode (here is a link that can help you: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode) and state the version id occurs on.

Thank you!

Comment 4

[Jamie Nicol [:jnicol]]

Hi! Since this is a recent regression, would you be able to use mozregression to identify what the cause is? You can install mozregression from here: https://mozilla.github.io/mozregression/install.html . Please ask if you need any assistance using it.

Comment 5

[limeclipse]

It occurs on Firefox Version 69.0.1 (20190917135527). It does not occur on safe-mode. Then in normal mode, it still occurs with all add-ons disabled, but does not occur when Hardware Acceleration is turned off. Hardware acceleration 'on' with "use recommended performance settings" 'off' the problem also remains.

It still occurs in 71.0a1 (20190925095053) nightly.

I used mozregression and this is as far I was able to pinpoint:
68.0a1 (20190418221600) (2019-04-18): Issue not present
68.0a1 (20190514214217) (2019-05-14): Issue present

Comment 6

[Daniel Bodea [:danibodea]]

You should help us further by performing a bisection with mozregression. I will try to be as clear as possible about how to do it:

1. You have to determine a build that reproduces the issue. You have already done that: 68.0a1 (20190514214217) (2019-05-14);
2. Then you should find one that does NOT reproduce it. It also appears that you've already done that: 68.0a1 (20190418221600) (2019-04-18);
3. You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
   a. Open mozregression-gui.exe
   b. Click "File" -> "Run a new bisection"
   c. On "Basic configuration" screen, select Build Type: "opt" and click "Next" button.
   d. Skip "Profile selection" screen by the "Next" button.
   e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
   e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found not to reproduce the issue.
   e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found not to reproduce the issue.
   f. Click "Finish" to start the bisection process.
   g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
   h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
4. Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you!

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Comment 8

[Liz Henry (:lizzard) (relman/hg->git project)]

Not sure we have enough information to go on here as the bug is hard to reproduce without specific hardware and, I think, paid accounts.

Comment 9

[Daniel Bodea [:danibodea]]

limeclipse, can you help us address your bug further? We would really need you to perform the instructions in comment 6. Thanks.

Comment 10

[limeclipse]

Attachment: Bisection

As it turns out I originally misidentified the last good build: When this guy was not clicked away, the full-screen video would play. It freezes the moment I closed it.

Last good build: 2018-09-12
First bad build: 2018-09-13

I attached the log file. The bisection ended without enough data.

Comment 11

[limeclipse]

I'd like to add despite the last good build being 2018-09-12, I'm very confident the issue started just before august this year.

Comment 12

[u650836]

I can confirm the bug. I have seen similar behavior in UWP video playback apps.

Comment 13

[daiyingw]

also have same issue with ff 79, geforce experience 3.20.4.14 and moonlight 5.0.1
workaround for me was to go to about:config, add 'media.windows-media-foundation.allow-d3d11-dxva ' and set to false

Comment 14

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.