Home Dashboard Directory Help
Search

When using CacheMode=BitmapCache, upon waking up from sleep WPF rendering thread consumes 40% CPU by bankoh


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


3
0
Sign in
to vote
Type: Bug
ID: 602232
Opened: 9/20/2010 7:09:09 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I have an app with a list box with FluidBehavior applied to the items. Additionally, the items can be expanded or collapsed and they are animated between these states. The animation appeared choppy at times, so I applied CacheMode=BitmapCahce to a part of the item template .
That worked fine and I could see the caching taking place using WpfPerf. However , when the machines would go to sleep and wake up, the window that contains cached elements appeared hung with the WPF rendering thread consuming 40% CPU. The other funcionality ( other windows, self hosted WCF services ) still worked.
Details
Sign in to post a comment.
Posted by Steven Jeuris on 5/14/2012 at 4:01 PM
Related: http://communities.intel.com/thread/20739
Posted by Steven Jeuris on 5/14/2012 at 3:56 PM
Unfortunately my current attempts at recreating the bug in a small project have failed. Although in my existing project there is a clear difference when enabling or disabling BitmapCache. In an attempt to diagnose the problem further I used Perforator to see whether anything interesting was going on. For some reason when going to sleep (or even just the log in screen) the video memory is lost. This doesn't happen when CachMode isn't enabled.

Here is a screenshot: http://i.imgur.com/GABpn.png
Posted by Steven Jeuris on 5/14/2012 at 10:37 AM
I can reproduce this issue. The application doesn't crash entirely, but the GUI does. E.g. I can still handle events and shut down. You won't be able to reproduce this looking for a crash, you will have to check the CPU usage, and verify that the GUI no longer responds. I will attach a small test project.
Posted by Microsoft on 9/29/2010 at 12:29 AM
Hi, given that we have not heard back from you, we will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.(Click “Edit this item” button on the site and change the “Status” to “Active”)
Posted by Microsoft on 9/21/2010 at 9:47 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a mini dump file and call stack. You can use the following steps to get a mini dump file:
1. Start Visual Studio.
2. Start another instance of VS.
3. In the second instance click Tools | Attach to Process...
4. In the list of processes locate devenv.exe.
5. Click Select... and explicitly choose 'Native' and 'Managed' code.
6. Click OK and OK to close Select dialog and Attach to Process dialog.
7. Go back to the first instance of VS and repro the crash\hang.
8. Upon the crash\hang, control should go to the second instance of VS.
9. In the second instance click Debug | Save Mini Dump (without heap).

If you are running the VB profile you will not see the Save Dump As menu item. To add this menu item:
a. Select Tools -> Customize
b. Select the Commands tab
c. Select Debug from the “Menu bar” dropdown
d. Click “Add Command…”
e. Select Debug from the Categories list.
f. Find the “Save Dump As” entry in the Commands window.
g. Click OK (the “Save Dump As…[mini dump ](without heap)” command is added to the top of the Debug menu).
h. Click “Close”

You can get detailed steps about how to get the dump file and call stack at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

Please name the zipped file Feedback-Id602232.zip.
You can upload the file to workspace:

https://sftasia.one.microsoft.com/choosetransfer.aspx?key=c4ba7ced-aae9-4adf-98fe-08ff1c857488
Password: #Tejy))YPc
It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Posted by Microsoft on 9/20/2010 at 8:16 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Could you please attach a zipped project file to this feedback through our site to help us reproduce the issue?

Thanks again for your efforts and we look forward to hearing from you.
Sign in to post a workaround.