I’ve got WPF application built with .NET 8, at some point it suddenly spiked both on CPU and memory. I managed to capture memory snapshot and it seems like there are lots of TimerQueueTimer objects allocated, not sure where did they come from.
Here’s a screenshot:
Did anyone have anything like that? I’ve seen it here: Too many TimerQueueTimer objects getting allocated and consuming high memory
But that was an ASP.NET application and problem was solved by updating to ASP.NET Core, while mine is WPF.
Application was running fine for ~1 day, but suddenly spiked on CPU and memory consumption. It should normally consume no more ~100M of managed memory.
Aydar Shamsutdinov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2