WPF密集UI处理导致ContextSwitchDeadlock

Question

我有一个WPF图表应用程序。基本上，用户从文件输入数据，应用程序对数据进行图表。当点的图表中的数量变得非常大，我得到的是说

The CLR has been unable to transition from COM context 0x23cda8 to COM context 0x23cf18 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

现在ContextSwitchDeadlock错误，我意识到这是因为UI线程不应该是忙不过来长，但我不清楚我的选择是什么，因为整个时间都花在向用户界面添加组件。如果我经常访问UI元素，我不能使用BackGroundWorker。那么我该从哪里出发？

Answer 1

有这么多的视觉效果真的很实际吗？如果是这样，我会打破添加视觉效果，并在单独的消息中做每一个。换句话说，使用Dispatcher将消息与适当的DispatcherPriority进行排队。每条消息将负责从总数中添加一小部分视觉效果。