WPFFontCache CPU usage 100% - by msmeja

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 651027 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 3/12/2011 3:08:04 AM
Access Restriction Public


We use Windows XP Embedded on our systems (>300 PC).
There are .NET framework 2.0 and 4.0 installed.
We use a WPF application and every day from the 300 PCs 4-5 reports this FontCache CPU problem.
The process (or service) using 100% the CPU.
We stop the service, remove the fontcache data files, and set the service to Disabled.
Sign in to post a comment.
Posted by Geert van Horrik on 3/28/2011 at 4:26 AM
We had a similar issue. When we were using a font size of 10, the software freezed and was using all the CPU available. When changing the font size to 9 or 11 (or just something NOT 10), it all works perfect.

We were using WPF and .NET Framework 3.5 SP1 (but the presentation cache version is 2.0). Using exactly the same code for .NET Framework 4 worked like a charm.

Then, we stopped the font cache service, but when starting our test app, it was automatically started again. Then we decided to disable the service and then the problem disappeared.

We are using Windows XP, intel on-board Q45/Q43 graphics card.

The strange thing is that this happens after a while, thus somehow it looks like the presentation cache gets corrupted, but we have not found the real reason yet.
Posted by msmeja on 3/21/2011 at 3:29 AM
When adding 1 new font to the Fonts the issue is resolved.
Otherwise WPF applications can not start! It's bug and a critical one...
Posted by Microsoft on 3/16/2011 at 2:34 AM
Thanks again for your feedback. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by msmeja on 3/14/2011 at 8:38 AM
Attached the file.
Anohter way to resolve the issue: add new fonts to the system. In this case something happens that resolves the bug and the WPF application can start.

Posted by Microsoft on 3/13/2011 at 11:38 PM
Thank you for reporting this issue.
Could you please type DXDiag in command line, Click Save All Information, and then attach the resulting dxdiag.txt file: http://support.microsoft.com/kb/190900

Posted by Microsoft on 3/13/2011 at 7:08 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)