Dispatcher MemoryLeak

[IAmTheCShark]

When investigating a memory leak using a process dump from a client, I noticed that there are lots of Dispatchers

When you take a close look on the first screenshot at paths to root it looks like Dispatchers are holding references of each other.
To my understanding a Dispatcher is connected to a Thread, so how can this happen?

The actual problem is that those dispatchers seem to hold lots of references

Sadly I do not know how to reproduce this, I only have the process dump (3.5 GB).
The Application uses lots of FlowDocuments and some WindowsFormsHosts.

Observed in .net 4.8 on a TerminalServer without RemoteGFX (software rendering).

[gurpreet-wpf]

@IAmTheCShark Can you please attach the sample repro?

[IAmTheCShark]

Unfortunately I can't.
Have tried quite a while. So i guess there is not much you can do either.

[lindexi]

@IAmTheCShark I do not think so. The object be captured by MediaContext, and it means that the object is rendering. In other words, the UI is using this object. You are confused by dotMemory, and this is just one of the reference paths.

[IAmTheCShark]

@lindexi i am not entirely convinced, but lacking a reproducable example I will close this for now.
The other concerning thing is the ammount of Dispatchers, not just the "holding itself" thing.
If I ever manage to reproduce this, I will open a new issue.

[lindexi]

@IAmTheCShark I look forward to your demo, thank you.