High memory consumption or memory leak on Intel integrated graphics
5 points · Open discussiondotnet
wpf
C#2018–2025
dotnet / wpf
wpf
WPF is a .NET Core UI framework for building Windows desktop applications.
27Distinct people
31Mentions
0Explicit recommenders
7.8KGitHub stars
What to know before exploring
What it is
WPF is a .NET Core UI framework for building Windows desktop applications.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/winforms · linked in 3 of the same discussions
- microsoft/microsoft-ui-xaml · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year31 dated mentions
Observed mentions: 2018-12-04 18:26:14 UTC to 2025-03-08 00:31:25 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Windows Presentation Foundation (WPF)
Windows Presentation Foundation (WPF) is a UI framework for building Windows desktop applications.
WPF supports a broad set of application development features, including an application model, resources, controls, graphics, layout, data binding and documents. WPF uses the Extensible Application Markup Language (XAML) to provide a declarative model for application programming.
WPF's rendering is vector-based, which enables applications to look great on high DPI monitors, as they can be infinitely scaled. WPF also includes a flexible hosting model, which makes it straightforward to host a video in a button, for example.
Visual Studio's designer, as well as Visual Studio Blend, make it easy to build WPF applications, with drag-and-drop and/or direct editing of XAML markup.
As of .NET 6.0, WPF supports ARM64.
See the WPF Roadmap to learn about project priorities, status and ship dates.
WinForms is another UI framework for building Windows desktop applications that is supported on .NET (7.0.x/6.0.x). WPF and WinForms applications only run on Windows. They are part of the Microsoft.NET.Sdk.WindowsDesktop SDK. You are recommended to use the most recent version of Visual Studio to develop WPF and WinForms applications for .NET.
To build the WPF repo and contribute features and fixes for .NET 8.0, Visual Studio 2022 Preview is required.
Getting started
.NET 6.0 SDK, .NET 7.0 SDK, .NET 8.0 SDK, .NET 9.0 SDK
.NET Preview SDKs
Getting started instructions
Contributing guide
Migrating .NET Framework WPF Apps to .NET Core
Status
We are currently developing WPF for .NET 10.
See the WPF roadmap to learn about the schedule for specific WPF components.
Test published at separate repo Tests and have limited coverage at this time. We will add more tests, however, it will be a progressive process.
The Visual Studio WPF designer is now available as part of Visual Studio 2019.
How to Engage, Contribute and Provide Feedback
Some of the best ways to contribute are to try things out, file bugs, join in design conversations, and fix issues.
This repo defines contributing guidelines and also follows the more general .NET Core contributing guide.
If you have a question or have found a bug, file an issue.
Use daily builds if you want to contribute and stay up to date with the team.
.NET Framework issues
Issues with .NET Framework, including WPF, should be filed on VS developer community,
or Product Support.
They should not be filed on this repo.
Relationship to .NET Framework
This code base is a fork of the WPF code in the .NET Framework. .NET Core 3.0 was released with a goal of WPF having parity with the .NET Framework version. Over time, the two implementations may diverge.
The Update on .NET Core 3.0 and .NET Framework 4.8 provides a good description of the forward-looking differences between .NET Core and .NET Framework.
This update states how going forward .NET Core is the future of .NET. and .NET Framework 4.8 will be the last major version of .NET Framework.
Code of Conduct
This project uses the .NET Foundation Code of Conduct to define expected conduct in our community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a project maintainer at conduct@dotnetfoundation.org.
Reporting security issues and security bugs
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Also see info about related Microsoft .NET Core and ASP.NET Core Bug Bounty Program.
License
.NET Core (including the WPF repo) is licensed under the MIT license.
.NET Foundation
.NET Core WPF is a .NET Foundation project.
See the .NET home repo to find other .NET-related projects.
Read the full README on GitHubWhat Hacker News says
31 sourcesWPF is not the best example of open source, as some components are still closed source. Though it only runs on Windows, a closed source operating system, so perhaps that is not so important.
https://github.com/dotnet/wpf/issues/2554
That said, there are cross platform, open source .NET UI frameworks out there, including one that is inspired by WPF:
https://avaloniaui.net/
In The search for easier safe systems programmingWPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.
In Something Pretty Right: The History and Legacy of Visual BasicThis article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:
https://github.com/dotnet/wpf/discussions/7130#discussioncom...
> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.
See also the recently updated WPF roadmap:
https://github.com/dotnet/wpf/blob/main/roadmap.md
If you look at the history of this file you can over the years tests have been always been in the backlog.
As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say t
Read the rest
hey don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.
WPF on .NET 6 is native-on-ARM64 now, apparently:
* https://developer.arm.com/documentation/102341/0400/WPF-and-...
* https://github.com/dotnet/wpf/issues/1817
* https://devblogs.microsoft.com/dotnet/net-july-2021/#windows...
> Windows Forms and WPF are now supported on Windows Arm64. We added support for Windows Arm64 with .NET 6 Preview 1 and have since backported it to .NET 5 (with 5.0.8). Windows Forms and WPF work the same on Arm64 as they do on x64. You could already use x86 emulation to run Windows Forms and WPF apps on Arm64, however, there was a performance cost to doing so. With this release, you can your apps natively with full performance.
In Available Today: Windows Dev Kit 2023 a.k.a. Project VolterraWPF is now open source (MIT licensed [1]), and its XAML control templates provide _as data_ a full declarative description of how a native Windows control is supposed to look like (in multiple Windows themes like Aero for Win7, Aero2 for Win10, Luna + Royale for WinXP, and Classic for Win95 look and feel [2]).
This includes everything like the exact colors and gradient stops and animation timing and vector shapes and accessibility behavior etc. of buttons and scrollbars and everything. Example: [3]
I wonder what one could learn / achieve trying to "port WPF to rust" / implement a XAML control template renderer in Rust. If you can "simply" parse and interpret those XAML files do you instantly get a native-like GUI that supports the exact look and feel of these different Windows themes? (on any OS!)
Somehow I think it is not realized how am
Read the rest
I don't get why people are repeating that. WPF is not dead, it's fully supported and the project has a future roadmap. (https://github.com/dotnet/wpf/blob/main/roadmap.md) MAUI is not taking over, it's not even released yet. We only just got a release candidate 3 this month. Looking at local job postings, WPF had hundreds of hits, while MAUI has... 3 "xamarin or maui" mentions.
In .NET 7 introduces Native AOT> walled garden
https://github.com/dotnet/wpf
In Don't forget MicrosoftFrom the outside it seems to be in maintenance mode. It hasn't received new features in a decade (other than the port to .NET Core, if that counts). The Windows team has staffed it with a skeleton crew (a manager and 2 devs last I checked). They don't have bandwidth to review most community PRs, and even the .NET team doesn't get responses to issues: https://github.com/dotnet/wpf/issues/3811
idk, I hope I'm wrong but they have been promising improvements for a while and I'll believe it when I see it.
In Does Visual Studio rot the mind? (2005)I won't speculate on things, but I will say that WPF is far from abandoned: https://github.com/dotnet/wpf/blob/main/roadmap.md
In Does Visual Studio rot the mind? (2005)Neither WPF nor WinUI are using OS controls for most of their GUI. Their GUI is defined by styles and templates in various XAML files. You can make controls look however you like. Microsoft did a great job back then re-implementing UX of WinXP and Win7 on top of WPF, but unfortunately not the newer Windows versions.
Here’s a third-party project with styles and templates implementing GUI similar to Win10: https://github.com/Kinnara/ModernWpf Their approach seems correct, and the screenshots looking nice. I never needed that library BTW, my clients who need good GUI usually provide professionally-made design which is unrelated to Windows controls.
Also, here’s a relevant GitHub issue https://github.com/dotnet/wpf/issues/5793 which currently says “.NET 7.0 milestone”, however the 7.0 is scheduled for November 2022, i.e. in about 1 year, and
Read the rest
they may or may not deliver by then.
It's a similar thing IMO. WPF is understaffed to the point where it might as well be dead in my mind.
It hasn't received major new features in a decade. It's currently owned by the Windows team (not the .NET team) and they have staffed it with a skeleton crew. They don't even have bandwidth to review most community PRs.
Even the .NET team doesn't get responses to issues they raise on the WPF repo: https://github.com/dotnet/wpf/issues/3811
Adding to all that, WPF has a massive dependency on C++/CLI which means it cannot take advantage of many new .NET features until that is rewritten. And from what I can tell (from the outside) that will never happen.
In I Rewrote WinUI to WPFIt is still actively developed, even if it doesn't get the same WinUI love.
https://github.com/dotnet/wpf
But yeah, having ramped down the team while beting the farm into WinRT wasn't the best idea.
Still, just like VB 6 in Windows 10, WPF will be around for decades to come and it isn't like there are revolutionary UI concepts to implement.
In The operating system: should there be one? (2013) [pdf]Indees it seems to be a dead end.
https://github.com/dotnet/wpf/issues/48
Thanks for clarifying.
In Performance Improvements in .NET 6Showing the 15 most recent of 31 sources. Enable JavaScript to search and browse every indexed mention.