IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
115 stars 4 forks source link

Discord screen sharing application crash #748

Closed BlauerToad closed 3 months ago

BlauerToad commented 6 months ago

Checklist [README]

Application [Required]

Discord

Processor / Processor Number [Required]

AMD Ryzen 5 2600X

Graphic Card [Required]

Intel Arc A770 16GB LE

GPU Driver Version [Required]

31.0.101.5379

Other GPU Driver version

31.0.101.5382 31.0.101.5444 31.0.101.5445

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

Open Discord, join any voice channel and start streaming your entire screen.

Update: The problem seems to be related to the transmission quality of the screen sharing.

Using the "Smoother video" quality setting, Discord operates fine; however, selecting the "better readability of texts" quality setting leads to the mentioned application crash.

Notes:

  1. the error almost always occurs. Streaming sometimes works after a restart, but very rarely.
  2. while the entire screen cannot be streamed, sometimes the individual applications can still be streamed (e.g. VS Code, Discord itself, IGCIT Helper). However, this does not mean that all application streams always work. Microsoft Edge application streams may or may not work.
  3. deactivating hardware acceleration solves the problem.

https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/assets/92584570/a1d12a40-22f9-4c04-b233-52920fc0e323

Device / Platform

Monitor Information: Alienware AW2724DM - 2560x1440

Crash dumps [Required, if applicable]

No crash dumps could be extracted with the IGCIT Helper.

Application / Windows logs

I haven't found any logs from Discord either

phyziyx commented 6 months ago

Occurs for me as well, and from what I understand, it has to do with hardware acceleration. This issue is reproducible on all Chromium (CEF) based applications. If your application does not crash, it'll black out the screen (for example, a video player on YouTube which uses HW accel)

BlauerToad commented 6 months ago

it has to do with hardware acceleration

Well it seems so. As stated above, discord does not crash anymore when hardware acceleration is turned off.

If your application does not crash, it'll black out the screen (for example, a video player on YouTube which uses HW accel)

Just tried screen sharing Microsoft Edge (just the application, not whole screen) and scrolling through YouTube and watching some videos, nothing got blacked out for the viewers of my the stream.

But I'm not sure if I understood your message correctly. Please feel free to correct me if I misunderstood it.

phyziyx commented 6 months ago

For example, if there was a YouTube video being played on an unfocused tab, and your current tab has another video playback or some other "effect" it will cause your entire screen to flash to black, and the video playback on the unfocused tab will 'freeze' and the [video] player will be completely black. It's almost as if the GPU driver has timed out [but it hasn't!]

I could reproduce the screen blackout consistently on Steam Community/Store or another website such as steampeek DOT hu.

BlauerToad commented 6 months ago

So, lastly, I encountered this "blacked-out screen" issue too. I searched Steam for games and opened some search results in new Steam browser tabs. Having the main Steam window unfocused and watching a game trailer in one of those "popup" Steam browser tabs, eventually every Steam window got blacked out and Steam crashed after multiple of those occurrences. It could be, that toggling full-screen was accelerating those blackouts.

phyziyx commented 5 months ago

image

Is this ever going to be looked into or resolved? I had this crash on a game now, and the only solution is to completely disable CEF acceleration in every application (some may not even offer such an option!)

BlauerToad commented 5 months ago

I would also appreciate feedback on whether the problem has been noticed.

Felipe-Intel commented 5 months ago

Hello @BlauerToad sorry for the delay. I have to set up my lab system for this. I was working with a couple other things. Rest assure I'll communicate my results and actions once I run the lab.

BlauerToad commented 5 months ago

Hello @Felipe-Intel, no worries about the delay. Looking forward to hearing about your results. Thanks for keeping us updated.

BlauerToad commented 5 months ago

I have just noticed that the application crash seems to be related to the transmission quality of the screen sharing. I updated my original issue.

Using the "Smoother video" quality setting, Discord operates fine; however, selecting the "better readability of texts" quality setting leads to the mentioned application crash.

I have also added my monitor information. Maybe there is a specific problem with the resolution.

Monitor Information: Alienware AW2724DM - 2560x1440

Felipe-Intel commented 5 months ago

@BlauerToad I was able to reproduce the issue. It seems to be related only to "screen" sharing, not to "window" sharing (I have to run more tests). I'll try to get the logs and dumps needed to debug this issue.

Felipe-Intel commented 4 months ago

Hello all. Just tested again with driver 101.5445 and the app is not crashing: screen share + text readability. Can you check on your side if you still see the issue?

BlauerToad commented 4 months ago

Hello, thanks for checking back. I am still facing the crash.

Edit: Just did an additional DDU run as well. However, the issue persists on my side.

Felipe-Intel commented 4 months ago

Thanks for testing. For some reason in my system doesn't fail right away after installing a new driver, but I get it to fail again. This issue seems to be happening only on Windows 10. We suggest to upgrade your system to Windows 11 to avoid this issue. 

If you prefer or have to stay on Windows 10, please try one the following workarounds:

Finally, please report this issue to Microsoft Windows Support.

We will do our due diligence in promoting this issue to MSFT from our end and co-work to try to find a solution. Said that, Windows 10 support will end October, 2025. We can't commit to time frame for this to be fixed. Would it be ok if we close this ticket? Please share your ticket number with Microsoft so we can add it to our report.

BlauerToad commented 4 months ago

Thank you as well,

at least the error is reproducible and not a “but it works on my machine” type.

I still have some questions:

Thanks for your investigations.

Felipe-Intel commented 4 months ago

@BlauerToad we got some feedback from our on-site point of contact with Microsoft. We will continue debugging this with them. I'll keep this ticket open and update you with news as soon as I have them. In the meantime you can still follow the workaround options I posted before. A third one is to force Windows to use the integrated graphics instead, but this is not possible in your specific case.

From your side, there is no need to create a ticket with Microsoft. For future reference, you can go "contact them" or "ask the community"

phyziyx commented 4 months ago

I know this is a Discord specific report, but I guess this also applies to Google Meet on Chromium/Google Chrome when sharing entire screen. Although the application does not crash, there is an entire black screen for a mere second or two. Perhaps this is related?

Felipe-Intel commented 3 months ago

Hi all, this was in the end root caused to the OS. So as mentioned before, if you want to report this issue, follow the links in my previous comment. And if you must stay in Win10, remember the workaround to avoid crashes.

I will proceed to close this issue.

BlauerToad commented 3 months ago

Hi Felipe, thanks for checking back. Do you have any further information for us? Will this issue be fixed in future Windows 10 Updates? Since you investigated the issue with Microsoft, they should aready know about it. I hope it does not need hundreds of mad useres reporting this issue further to Microsoft, that they will hopefully fix it.

As it seems, this issue only occurs with Intel Arc graphic cards (neither AMD nor Nvidia), I also see Intel as having a responsibility to tell Microsoft to fix this problem. We all know, that Windows 10 will be EOL Oct. 2025, but we also know that Windows 10's market share is still on par with Windows 11.

So I hope that this issue will not be played down and that Intel will still work towards a solution.

Felipe-Intel commented 3 months ago

For updates on this issue, please check this article

BlauerToad commented 3 months ago

Thank you for your assistance 👍