WebView2Feedback icon indicating copy to clipboard operation
WebView2Feedback copied to clipboard

[Problem/Bug]: After a period of time, the video element will not display the picture and only play the sound.

Open HHGGHH1995 opened this issue 4 months ago • 2 comments

What happened?

I embedded a video player element in a webpage, hiding all of its controls, such as the progress bar and volume, and used it as a dynamic background for the page. The video would also switch between them periodically. I found that there were no issues at first, with both the video display and the sound playing normally. However, when I left the computer idle for a while, I noticed that the video no longer displayed, while the sound continued to play normally. I would also like to clarify that the computer did not automatically hibernate or sleep when idle. When encountering the above situation, refreshing the page cannot solve the problem. The video screen is still not displayed, only the audio is played. It will return to normal only after restarting the process.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

138.0.3351.83

SDK Version

No response

Framework

Winforms

Operating System

Windows 10

OS Version

10.0.19045.0

Repro steps

Embedding a video player element in a page and switching the video source regularly will cause the video to not display after a certain period of time.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

HHGGHH1995 avatar Aug 18 '25 03:08 HHGGHH1995

hi @HHGGHH1995 can you please provide the SDK Version and the respective sample app you are referring to which you are facing issue. If possible, please provide the video or a screen shot of the bug you are facing. Thankyou

vootlasaichandu avatar Aug 19 '25 09:08 vootlasaichandu

I have the same issue, i've tried many SDK versions including the latest, all present the same issue. Issue has started to occur since Build 139.0.3405.102 of the runtime has been "evergreened" onto our devices

The failing devices are win10 IoT Enterprise LTSC. Seems fine on Standard editions of windows (in my case)

bitsnpeices avatar Aug 23 '25 08:08 bitsnpeices