Hi Sorin,

Does the behaviour change if you print, close the app, restart and reprint?

Have you tried uninstall the KB5000802 (on WIN10 2004) that led to to the recent BSOD?

Just curious. I do paint DataMatrix codes on reports via report listener- and this is a major task. Don't like to run into a trap.


But then. You say it's on REPORTBEHAVIOR 80 too? Was'nt it the diff that 90 uses GDI+ and 80 not? Odd.

Lutz

>Thank you, Lutz!
>As I wrote in my earlier post, I confirm it is a GDI problem and apparently not related to specific printer drivers. The first thing we tried was applying the patch from KB5001567, but that didn't seem to have an effect on this issue.
>My test shows that GDI objects are not freed in versions 2004 and 20H2. For now, the only solution would be to revert to 1909. I am still curious to see what results others would get when running my test.
>
>>>VFP9 SP2 on Windows 10 20H2
>>>Suddenly, we started receiving complaints re report printing from several clients who have been using our app with no such issues until today. The reports are normal daily reports; 10 - 20 pages.
>>>What we determined, so far:
>>>When report is run for the first time, it prints ok on several pages (6 - 7 pages), after which it outputs all pages blank. As soon as that happens, any attempts to run reports result in blank output to printer (or PDF with 0 KB), trashed display of form controls on screen, images missing from toolbar buttons, etc. Eventually, the app will crash either with a "Resource manager internal consistency error" or with "GDI+ insufficient resources".
>>>We suspect that a recent W10 update may have something to do with it.
>>>* Tested REPORTBEHAVIOR 80 and 90 with the same results
>>>* We looked for registry settings for GDIProcessHandleQuota and USERProcessHandleQuota, but apparently they're not preset in Windows 10.
>>>Any other suggestions appreciated.
>>>TIA