Open Bug 1903455 Opened 8 months ago Updated 4 months ago

Rtx Video Super-resolution stops working

Categories

(Core :: Graphics, defect, P3)

Product:
Core
Component:
Graphics
Version:
Firefox 127
Platform:
Desktop
Windows 11
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: ricky052000, Assigned: sotaro, NeedInfo)

References

Details

Attachments

(2 files)

Firefox Info
61.77 KB, application/octet-stream
Details
about profile 2.txt
74.14 KB, text/plain
Details

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

Steps to reproduce:

With Rtx video super-resolution enabled, minimizing the video on youtube, changing to a different tab, then coming back to the video in fullscreen mode causes the video to flicker. Playing 1080p60/1440p60 at speeds higher than 1x caused the same flicker.

Hardware used:
Cpu: Ryzen 7 7800x3d
Gpu: Nvidia Rtx 4090

Actual results:

Video would flicker and the feature turns off. The only way to turn it back on, is by completely restarting the browser

Expected results:

Video should re-enable the feature when returning to the original tab. At speeds higher than 1x, feature should remain enabled as well

OS: Unspecified → Windows 11
Hardware: Unspecified → Desktop

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics
Product: Firefox → Core
Flags: needinfo?(sotaro.ikeda.g)
Blocks: gfx-triage
Severity: -- → S2

Please go to the url about:support and click either of the copy to clipboard buttons at the top and paste into a new attachment on this bug, it's important to know a few things about your monitor setup and other factors in understanding this bug.

Dropping Severity until we've done a full analysis.

Severity: S2 → S3
Flags: needinfo?(ricky052000)
Attached file Firefox Info —
Flags: needinfo?(ricky052000)

(In reply to Ashley Hale [:ahale] from comment #2)

Please go to the url about:support and click either of the copy to clipboard buttons at the top and paste into a new attachment on this bug, it's important to know a few things about your monitor setup and other factors in understanding this bug.

I've added the file

With my Win11 PC(with NVIDIA GeForce RTX 2060 SUPER), super resolution became active only with 480p and 360p. With 1080p60/1440p60, super resolution did not become active with the PC.

If super resolution was not active, the flicker might be related to Bug 1638709.

Can you take Firefox Profiler with "media" setting with latest nightly?
https://profiler.firefox.com/

Flags: needinfo?(sotaro.ikeda.g) → needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #6)

With my Win11 PC(with NVIDIA GeForce RTX 2060 SUPER), super resolution became active only with 480p and 360p. With 1080p60/1440p60, super resolution did not become active with the PC.

If super resolution was not active, the flicker might be related to Bug 1638709.

Can you take Firefox Profiler with "media" setting with latest nightly?
https://profiler.firefox.com/

I uploaded a link to google drive with the file you asked for. It's too big to upload here. I set the video to 1440p60, let it play at 2x speed in the small window on YouTube. Then made it full screen and it immediately turned off

Thank you. Local profile data could be uploaded just by pushing "Upload Local Profile" in the profile result UI like in instruction.

(In reply to Sotaro Ikeda [:sotaro] from comment #9)

Thank you. Local profile data could be uploaded just by pushing "Upload Local Profile" in the profile result UI like in instruction.

oh I didn't think I could do it directly like that. I'll keep it in mind for next time. Thanks

SuperResolution support/usage info exists in Marker Table in Profiler data UI like the following

DCSurfaceVideo - SuperResolution VP Capable 1 OtherFieldsValid 1 Enabled 1 InUse 0 Level 0

The marker exists from 6.038s to 19.132s. SuperResolution is not used from 6.038s to 18.822s.

SuperResolution is used only from 18.961s to 19.132s like the following

DCSurfaceVideo - SuperResolution VP Capable 1 OtherFieldsValid 1 Enabled 1 InUse 1 Level 4

From the above, SuperResolution usage seemed not directly related to the problem.

DragonicPrime, does the problem not happen when SuperResolution is disabled?

Flags: needinfo?(ricky052000)
See Also: → 1638709

(In reply to Sotaro Ikeda [:sotaro] from comment #11)

SuperResolution support/usage info exists in Marker Table in Profiler data UI like the following

DCSurfaceVideo - SuperResolution VP Capable 1 OtherFieldsValid 1 Enabled 1 InUse 0 Level 0

The marker exists from 6.038s to 19.132s. SuperResolution is not used from 6.038s to 18.822s.

SuperResolution is used only from 18.961s to 19.132s like the following

DCSurfaceVideo - SuperResolution VP Capable 1 OtherFieldsValid 1 Enabled 1 InUse 1 Level 4

From the above, SuperResolution usage seemed not directly related to the problem.

DragonicPrime, does the problem not happen when SuperResolution is disabled?

no there's no issue with SuperResolution disabled. Checking MSI afterburner as well, I see the GPU usage spike up for a second, then it almost immediately turns off. Same with looking at the Nvidia control panel. It says SuperResolution turns on for a moment, then back to Inactive

Flags: needinfo?(ricky052000)

Thank you for checking. So just enabling SuperResolution seemed to cause the problem.

Can you also check if the problem happens with only one display connected? I wonder if there was interaction like Bug 1638709.

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #13)

Thank you for checking. So just enabling SuperResolution seemed to cause the problem.

Can you also check if the problem happens with only one display connected? I wonder if there was interaction like Bug 1638709.

Seems like the same quick flash still happens, and SuperResolution turns off until restarting the browser like before

Flags: needinfo?(ricky052000)
Assignee: nobody → sotaro.ikeda.g
No longer blocks: gfx-triage
Priority: -- → P1

Thank you for the checking.

Can you also test again with latest driver? Latest driver seems 32.0.15.5612 (6-25-2024).

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #16)

Can you also test again with latest driver? Latest driver seems 32.0.15.5612 (6-25-2024).

The issue still stayed. I decided to completely uninstall firefox and any file related to firefox and reinstall it. It seems to actually be working now. I'll keep testing it just in case, but the quick flash that it was doing before isn't happening anymore and the feature stays enabled. Maybe something went wrong with the initial installation the first time? I didn't use the browser that often because the feature never seemed to work properly for me

Flags: needinfo?(ricky052000)

Seems like the issue isn't completely gone. While the quick flash and disabling of the feature doesn't happen anymore when opening a video in full screen or changing tabs, it does still seem to turn off on it's own after leaving the browser open for a while. I keep having to completely restart the browser every 30 minutes to an hour if I just leave it idle while doing other stuff, because Super Resolution just turns itself off

:ahale, can you check if the problem happens for you?

Flags: needinfo?(ahale)

From comment 17, the quick flash seemed to be addressed by re-installing.

DragonicPrime, can you upload about:support and take Firefox Profiler data after SuperResolution turn off on it's own after leaving the browser open for a while?

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #20)

From comment 17, the quick flash seemed to be addressed by re-installing.

DragonicPrime, can you upload about:support and take Firefox Profiler data after SuperResolution turn off on it's own after leaving the browser open for a while?

I was trying to do this, but it's not turning off now. I haven't used the browser in a few days. Was there an update? Nothing changed on my end. But now it doesn't turn off at all either while watching a video, or on it's own after leaving the browser open doing nothing. I'll use the browser again for a bit and report back if anything changes randomly again

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #20)

From comment 17, the quick flash seemed to be addressed by re-installing.

DragonicPrime, can you upload about:support and take Firefox Profiler data after SuperResolution turn off on it's own after leaving the browser open for a while?

https://share.firefox.dev/4bqMihq

Here is the the profiles data after SuperResolution turned off on its own. For the about:profile, is it better to copy raw data or text?

Hi DragonicPrime, I just wanted to confirm about:support and Firefox Profiler data since the reinstall of comment 17 for checking if there is a difference. Is it possible to get them again?

Flags: needinfo?(ricky052000)

(In reply to DragonicPrime from comment #22)

(In reply to Sotaro Ikeda [:sotaro] from comment #20)

From comment 17, the quick flash seemed to be addressed by re-installing.

DragonicPrime, can you upload about:support and take Firefox Profiler data after SuperResolution turn off on it's own after leaving the browser open for a while?

https://share.firefox.dev/4bqMihq

The link does not have full threads information during taking profile. For example, "GPU process" contains only "IPC-GPU process" and "MediaSupervisor #2". Is it possible to upload the data with full threads inforrmation?

(In reply to Sotaro Ikeda [:sotaro] from comment #24)

(In reply to DragonicPrime from comment #22)

(In reply to Sotaro Ikeda [:sotaro] from comment #20)

From comment 17, the quick flash seemed to be addressed by re-installing.

DragonicPrime, can you upload about:support and take Firefox Profiler data after SuperResolution turn off on it's own after leaving the browser open for a while?

https://share.firefox.dev/4bqMihq

The link does not have full threads information during taking profile. For example, "GPU process" contains only "IPC-GPU process" and "MediaSupervisor #2". Is it possible to upload the data with full threads inforrmation?

here is the new link for the profiling data: https://share.firefox.dev/4cy8Ez0
I tried to include as much thread data as possible. I also uploaded the about:support page data as well

Flags: needinfo?(ricky052000)
Attached file about profile 2.txt —

Thank you for data update! I got back from the PTOs.

Attachment 9411413 [details] has the following failure log. From it, video overlay of hardware decoded video was disabled by slow video overlay rendering. SuperResolution could be used only with video overlay. But the video overlay was disabled by slow present. Then SuperResolution was also disabled.

"failures": [
"[GFX1-]: Handling webrender error 6",
"GP+[GFX1-]: Hw video swapchain present is slow",
"[GFX1-]: Handling webrender error 6"
],

"Hw video swapchain present is slow" checks exists at the followings.

Priority: P1 → P3

For now, gecko need to keep the "Hw video swapchain present is slow" checks to avoid frame drop with video overlay.

Priority was dropped to P3 from comment 27 and comment 28.

Flags: needinfo?(ahale)

(In reply to Sotaro Ikeda [:sotaro] from comment #28)

For now, gecko need to keep the "Hw video swapchain present is slow" checks to avoid frame drop with video overlay.

gecko disables video overlays system-wide if the checks fails. It could be changed. Disabling the overlay could be applied only to the video causing the slowdown.

Created Bug 1908585 for comment 30.

Depends on: 1908585

DragonicPrime, can you check if the problem could happen with latest nightly? And can you also check if the problem could be addressed by re-loading the video?

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #32)

DragonicPrime, can you check if the problem could happen with latest nightly? And can you also check if the problem could be addressed by re-loading the video?

I've been testing the nightly build since the fix 13 days ago. It has been mostly working flawlessly. I've only just had a couple of times where the feature turned off, but just refreshing the page fixed it. I'm still not sure what caused that since it has only happened 2 or 3 times. The only other bug I've noticed was when I was fast forwarding through a video to see a specific part. I put the video on 3x just to get there faster. At 1440p60fps it can cause the video to freeze for 2-3 seconds then return back to normal. But it seems to happen repeatedly. I don't watch videos at that speed so it's not a big deal for me. Those are the only 2 small issues I've seen so far. Thanks for the help

Flags: needinfo?(ricky052000)

Thank you for checking!

But I just noticed that there is a report that Bug 1908585 caused the regression(Bug 1910637). The behavior might be changed by addressing Bug 1910637. Thank you.

Depends on: 1910637

Well seems like the newest nightly update broke it again. It was working fine before I updated it.

(In reply to DragonicPrime from comment #35)

Well seems like the newest nightly update broke it again. It was working fine before I updated it.

Does the problem addressed by reloading the video? At this time, there is no good way to distinguish this bug issue from Bug 1910637.

Flags: needinfo?(ricky052000)

(In reply to Sotaro Ikeda [:sotaro] from comment #36)

(In reply to DragonicPrime from comment #35)

Well seems like the newest nightly update broke it again. It was working fine before I updated it.

Does the problem addressed by reloading the video? At this time, there is no good way to distinguish this bug issue from Bug 1910637.

Yes I don't have to restart the browser, but at least with 1440p60fps videos, it stops working immediately as soon as I go info fullscreen just like before

Flags: needinfo?(ricky052000)

I just want to hop in and say I'm also having an issue with Super Resolution not working at all. This is my first comment I've ever made in bugzilla, so I apologize if I don't write it correctly or something.

I've tried everything I can reasonably, and unreasonably, come up with. I first confirmed it works in Chrome, both Super Resolution and Auto-HDR. I also tested it in Microsoft Edge, and only Auto-HDR worked, not Super Resolution. Either way, I feel like this is likely more of a Firefox issue.
I'm on Windows 10 Pro (22H2 19045.4651), Firefox Version 128.0.3, Nvidia Graphics Driver 560.70 on a 3070 Ti.
I was originally on the latest Studio Driver, but I decided to go with the latest Game Ready Driver to see if that would fix it.
In Windows, in the "Graphics settings" I have Hardware-accelerated GPU scheduling turned on (I've tried turning it off), and I have tried setting Firefox to "High performance".

In Firefox I have Use hardware acceleration when available enabled.
In a desperate attmpt, I went into about:config and changed following to true:
gfx.webrender.super-resolution.nvidia
gfx.webrender.overlay-vp-super-resolution
gfx.webrender.overlay-vp-auto-hdr
gfx.webrender.all
media.hardware-video-decoding.force-enabled

And finally, I have tried disabling Enhanced Tracking Protection for YouTube.

I know for certain that Super Resolution was working months ago, but unfortunately I had stopped using it at some point and so I don't know if it was a Firefox or Nvidia update that broke it, and if so, which update.

I'm sorry, I realized I didn't even include everything I had done. I also tried it in Troubleshoot Mode, and in the Nightly version. I would try Refresh, but I really don't want to go to that unless that is confirmed to be the only solution at this point.

I'm sorry again, I would delete my other comments if I knew how but I have finally found the solution to my issue. I still don't know if anything could be done on Firefox's end (considering that without the fix Chrome still works but Firefox doesn't), but the issue was that I had different refresh rates across multiple monitors. Once I had them all set to the same refresh rate, it would enable.
I found it from this Reddit comment mentioning that inside of about:support's Decision Log they found this error:
Blocklisted; failure code NVIDIA_REFRESH_RATE_MIXED

(In reply to Richard Simonson from comment #40)

Blocklisted; failure code NVIDIA_REFRESH_RATE_MIXED

This disables Windows DirectComposition(Bug 1704954), it causes disabling also video overlay, since video overlay requires DirectComposition.

SuperResolution works only with video overlay.

:ahale, do you know about current status of NVIDIA mixed refresh rate?

Flags: needinfo?(ahale)

So with the most recent update on the stable build of firefox(129.0), rtx video super resolution and rtx hdr both seem to be working flawlessly now. I'll keep testing it just in case it breaks again, but over the last couple of days, I've had 0 issues with it. With the nightly build it's still broken for me, and recently the rtx hdr feature also broke and looks terrible because all of the colours are wrong

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

(In reply to wesleylin000 from comment #45)

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

No I never got a solution for it. If I set the quality to auto, it breaks as well. Closest thing I've managed to do, is set the quality at 2 and it works with 0 issues no matter what resolution or playback speed. Quality is still good, but I can definitely tell it's not as clear as quality level 4

(In reply to DragonicPrime from comment #46)

(In reply to wesleylin000 from comment #45)

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

No I never got a solution for it. If I set the quality to auto, it breaks as well. Closest thing I've managed to do, is set the quality at 2 and it works with 0 issues no matter what resolution or playback speed. Quality is still good, but I can definitely tell it's not as clear as quality level 4

Ahhh damn. Do you beleive it may be the issue that Sotaro Ikeda mentioned with the difference monitor refresh rate. But even if that was the issue I have a 60hz 4K monitor with a 240hz 4K monitor as my main. No way I’m equalising the refresh rates.

(In reply to wesleylin000 from comment #47)

(In reply to DragonicPrime from comment #46)

(In reply to wesleylin000 from comment #45)

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

No I never got a solution for it. If I set the quality to auto, it breaks as well. Closest thing I've managed to do, is set the quality at 2 and it works with 0 issues no matter what resolution or playback speed. Quality is still good, but I can definitely tell it's not as clear as quality level 4

Ahhh damn. Do you beleive it may be the issue that Sotaro Ikeda mentioned with the difference monitor refresh rate. But even if that was the issue I have a 60hz 4K monitor with a 240hz 4K monitor as my main. No way I’m equalising the refresh rates.

well I tried it before by removing my secondary monitors and it still didn't work. Even if that was the case, I don't want to have to limit my 240hz monitor to less than that because of a bug that only happens on firefox and nothing else

(In reply to DragonicPrime from comment #48)

(In reply to wesleylin000 from comment #47)

(In reply to DragonicPrime from comment #46)

(In reply to wesleylin000 from comment #45)

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

No I never got a solution for it. If I set the quality to auto, it breaks as well. Closest thing I've managed to do, is set the quality at 2 and it works with 0 issues no matter what resolution or playback speed. Quality is still good, but I can definitely tell it's not as clear as quality level 4

Ahhh damn. Do you beleive it may be the issue that Sotaro Ikeda mentioned with the difference monitor refresh rate. But even if that was the issue I have a 60hz 4K monitor with a 240hz 4K monitor as my main. No way I’m equalising the refresh rates.

well I tried it before by removing my secondary monitors and it still didn't work. Even if that was the case, I don't want to have to limit my 240hz monitor to less than that because of a bug that only happens on firefox and nothing else

True. I will try with level 2 on super resolution. The issue also persists for me on chrome as well before I moved to Firefox. I thought moving to a different browser might fix it, but sadly it didn’t. I’m was thinking if it was a ram issue or if my PC couldn’t handle it. But I have a 5800x3d and a 4090 so I don’t believe that would be an issue.

(In reply to wesleylin000 from comment #49)

(In reply to DragonicPrime from comment #48)

(In reply to wesleylin000 from comment #47)

(In reply to DragonicPrime from comment #46)

(In reply to wesleylin000 from comment #45)

(In reply to DragonicPrime from comment #44)

Well I did some testing. The stable version that was working for a while just stopped for some reason. 1080p60 still works perfectly, but 1440p60 just doesn't work. Instantly breaks RTX SuperResolution and HDR. I tried the latest nightly build too. The broken HDR I was experiencing is fixed, but SuperResolution is the same as stable. 1080p60 works fine, 1440p60 is still broken

Did you end up finding a definitive solution to this? I’m currently facing the same issue where my super resolution and RTX HDR causes YouTube to flicker and refresh and turn off.

No I never got a solution for it. If I set the quality to auto, it breaks as well. Closest thing I've managed to do, is set the quality at 2 and it works with 0 issues no matter what resolution or playback speed. Quality is still good, but I can definitely tell it's not as clear as quality level 4

Ahhh damn. Do you beleive it may be the issue that Sotaro Ikeda mentioned with the difference monitor refresh rate. But even if that was the issue I have a 60hz 4K monitor with a 240hz 4K monitor as my main. No way I’m equalising the refresh rates.

well I tried it before by removing my secondary monitors and it still didn't work. Even if that was the case, I don't want to have to limit my 240hz monitor to less than that because of a bug that only happens on firefox and nothing else

True. I will try with level 2 on super resolution. The issue also persists for me on chrome as well before I moved to Firefox. I thought moving to a different browser might fix it, but sadly it didn’t. I’m was thinking if it was a ram issue or if my PC couldn’t handle it. But I have a 5800x3d and a 4090 so I don’t believe that would be an issue.

Not sure what could be causing your issue then. I don't use chrome so idk if it works there, but I've tried it on brave, edge, opera and vivaldi and they all work flawlessly. I assume it's because they're all chromium

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: