dotnet / wpf

WPF is a .NET Core UI framework for building Windows desktop applications.
MIT License
7.08k stars 1.17k forks source link

The .Net Core WPF program UI errors #2493

Closed ssc19940105 closed 4 years ago

ssc19940105 commented 4 years ago
gomathip02 commented 4 years ago

@ssc19940105 - Pls share repro app, screenshots and also pls describe the problem in detail.

ghost commented 4 years ago

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your contributions!

ssc19940105 commented 4 years ago

I will provide the required information later

ssc19940105 commented 4 years ago

This is the video of the program running. NC31 WPF UI Render Error.zip

weltkante commented 4 years ago

@rladuca @vatsan-madhavan the bot seems to be misbehaving and closing the issue even though a response by the issue creator has been given?

rladuca commented 4 years ago

@weltkante Thanks for spotting it, sorry about that @ssc19940105, we'll look into the bot.

rladuca commented 4 years ago

This is likely related to #707. Can you check if you have one of the culprits listed in the bug installed on your system? I believe the list includes Nahimic and Realtek right now, but there are likely other pieces of SW incorporating these bad behaviors.

rladuca commented 4 years ago

@ssc19940105 This looks like an instance of #707. Likely this is due to a specific component interfering with WPF. Check for things like Realtek Sonic Studio and Nahimic software.

ssc19940105 commented 4 years ago

The program renders correctly after I try to close NahimicService.But I don't understand why .Net Framework is not affected.Is there any difference between them.

rladuca commented 4 years ago

@ssc19940105 This isn't a WPF issue but an issue with Nahimic's software. They are trapping certain calls and this is interfering with WPF rendering. In .NET Framework they don't seem to do this, meaning the software is detecting either a .NET or a WPF process and is not injecting into it. As was stated in the linked bug, WPF can't react to all possible changes like this, nor should it.

We're working as best we can to link up with various software vendors and make sure these issues are resolved.

For now I'll close this. Please use #707 to add onto the information as we are still monitoring this and working to try and get the offending software updated appropriately