Second monitor - video stutters / lags.
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: lkocik, Unassigned)
Details
Attachments
(1 file)
|
7.38 MB,
video/x-matroska
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
Video stutters / lags on the second monitor while scrolling the pages in the browser (one monitor - firefox browser, the other monitor - running video from another application). Occurs only in the case of Firefox browser - after the latest latest update.
Actual results:
When I run a movie / video in any resolution (be it 1080p, 720p, 30fps, 25, fps, 60 fps) on TV (the second monitor connected to the laptop) and at the same time I use the firefox browser - when scrolling / browsing video websites it starts to lag - frame. I tested on other browsers - the problem does not occur. It started appearing only after updating to the latest version of firefox. Captured problem in attachment - visible frames / jams occur when browsing web pages in firefox.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
It sounds like the performance issue is taking place in another program, is that correct? If that is the case it's going to be highly difficult to diagnose the interaction between Firefox and the other program that lead to the issue. The best bet would be profiling Firefox to see if it's using more resources than expected.
|
||
Comment 3•11 months ago
|
||
Just ran into this issue on a M2 Max 16 inch MBP, running Firefox Developer Edition: 124.0b7 and (just updated) 124.0b8. I also tried to reproduce this on a brand new profile and it also happens there - video and audio skips randomly when a youtube video is put on another window on the second monitor (internal monitor). The external monitor and the internal monitor are both running at 120hz (though the external is strict 120hz and the internal one is ProMotion).
I would love to provide more information if needed.
|
|
||
Comment 4•11 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:jimm, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Updated•9 months ago
|
|
||
Comment 5•4 months ago
|
||
I hesitate to add something to this rather old thread but it is so close to what I'm experiencing that I think I should comment here rather than open a new bug report.
Operating system: Windows 11 Pro 64-bit version 24H2 build 26100.2033
Firefox 131.0.2 64-bit (updated yesterday)
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0
Video adapter: NVidia GeForce RTX 4070.
I have 2 monitors, like the earlier poster. I am running them both at 1920x1080@60Hz. Monitor #1 is attached to the NVidia via HDMI-to-DisplayPort dongle. Monitor #2 is attached to the HDMI port on the NVidia. There is only 1 such port. Monitor #2 is my television. The third & fourth ports on the NVidia, both also DisplayPorts, have nothing attached. In Windows, I have the 2 monitors defined as being "extended," to use Microsoft's jargon.
When Firefox visits any web page where there is a video player embedded, example being YouTube but the problem occurs the same with other sites, playback in fullscreen on the primary monitor is fine. If I swap the Firefox window over to the second monitor & play the same content in fullscreen, it looks like claymation. Non-fullscreen plays fine on the second monitor.
If there is picture-in-picture available, I can stretch it out so the edges of the p-in-p aperture are close to the edges of the display area on monitor #2. You could call this almost-fullscreen. This plays fine. If I put the p-in-p to fullscreen on monitor #2, the claymation effect appears. If I use p-in-p on monitor #1, there is no problem, including in fullscreen.
When I play anything in VLC in fullscreen on monitor #2, there is no problem.
This was not a problem with Firefox 131.0, which is what I had before I updated to 131.0.2. I never had a 131.0.1 on my W11 box. I did have a 131.0.1 on my Android phone. I don't assume that the release numbering on the 2 platforms is always entirely identical. It often is, but not always, & apparently not with these latest sub-releases of Firefox 131. I do believe Firefox for Windows did skip 131.0.1. So I went from 131.0 which did not have this problem directly to 131.0.2 which does exhibit this anomalous behavior.
Description
•