Why WPF works on some systems

I have problems with the user interface performance of my WPF application on some systems. It works fine on my development system, on some other systems, but the performance is very poor. A problem arises, for example. when moving splitters, resizing FlowDocuments, or hovering over buttons.

The difference in performance is not directly related to the obvious "computer specifications." The application performs OK on the netbook (Intel Atom N550, 1 GB of RAM, Windows performance index: 2.0), but not on the desktop computer (I7 2600, 8 GB Ram, ATI Radeon HD 5700, Windows performance index: 7.4). Both systems are running Windows 7. The application is built using .NET 4.0. I tried to force the software to render using RenderOptions.ProcessRenderMode = RenderMode.SoftwareOnly. This, however, does not matter.

What causes this problem? How can i fix this?

+7
source share
2 answers

It looks like it might be a Wpf 4 bug that we stung, which affects applications with complex Wpf visual trees. It was discussed in this thread http://social.msdn.microsoft.com/Forums/en/windowsaccessibilityandautomation/thread/6c4465e2-207c-4277-a67f-e0f55eff0110 . This even affected the Workflow 4 constructor in VS 2010 - see http://social.msdn.microsoft.com/Forums/en/wfprerelease/thread/1f20c37f-1b9e-4b6d-904f-a6b518e4187a . There is a fix for this thread that you can try: http://support.microsoft.com/kb/2484841

You can get a good idea if this is a problem by linking the debugger to your application when it hangs / stutters and see if you see a lot of UiAutomation InvalidateAutomationAncestors frames on the stack.

+7
source

Perhaps the problem is x64 and x86? Setting up the target platform for any processor.

0
source

All Articles