Re: GDI/GDI+ stop drawing after a while on Windows 7

I have an app that I developed some time ago for W2K. The app draws text
and graphics onto a CView derived window using GDI+. It also hosts
shockwave flash player that occasionally plays a clip in the same window.
The app could work 24x7 on W2K and XP.

I'm now testing the app on Windows 7 Home Premium. I'm running into a
strange problem. After running it for a while - sometimes it could be a
couple of hours, another times a couple of days - the app simply stops
drawing to the screen. That is, the app still calls the necessary APIs
but nothing happens on the screen.

I'm logging the most important calls to a file with their return codes and
there are no errors reported whatsoever. In addition, the shockwave
object is not displaying anything either and does not report any errors.

Quitting the app and restarting it fixes the problem (i.e. for another
couple of hours/days). So it is not a system wide failure.

I'm monitoring the most important resources (e.g. memory, handles, etc.)
and did not see any leaks. The app is not hung either. The app's timers
and worker threads are running when the app runs into the problem. I
could also bring up a dialog box belonging to the app and move it around
without any problems.

I realise that Windows 7 with its Direct3D Aero/WDM has to 'emulate' GDIs
but I'd rather expect some performance issues and not a complete and
undetectable failure like this.

Could anyone please give some ideas/pointers about how to troubleshoot
this one?

Thanks,
Bogdan