Direct 2D Drawbot Error - Invalid Widnow Handle. HRESULT: -2147023496

Thanks very much to those that have reported this and helped us isolate the problem. I received a large (150 GB) project + media set from @Pitepx and I tested it quite extensively using recent Beta builds od Pr 25.2 and 25.3 as well as the current release version, which is Pr25.1x073. The only repro steps I know of are toy do a lot off shuttling, jogging, JKL playback in conjunction with some basic editing things like trimming and moving clips. 

So the good news is that the problem was not happening at all in any of my tests, including in the latest Pr 25.3 beta builds. But it also did not happen inthe relase version of 25.1. So I can't say for sure that it's fixed with @Peter_Antal 's latest changes, but it's looking good so far, at least from my point of view. Please, for those of you who have been experiencing the problem lately, can you upgrade to the latest beta build (Pr25.3xBeta003 or higher) and let us know if the problem will still happen for you? 

@Peter_Antal @jamieclarke after some time editing, the problem was still gone, then back, then gone again and honestly I can't know what I did to get it back, then gone, then back again. I'll be getting the project collect later today while I'm asleep since it will take a bit (it's a newer project with around 150 items so it is easier than the previous one which had like 2k)

Thanks for the follow-up - Sorry to hear on your folder loss. Hmm, so the problem disappeared or slowed down substantially at the moment? If your repro has decided to make itself disappear, we probably won't be able to see it either.

We did put out a fix for an issue related to leakage in progress view dashboard into beta prime last week. I wouldn't have expected that to be elicited with what you saw with timeline, but may possibly explain.
P: Transcription leads to errors, video artifacts,... - Adobe Community - 14987974

It's also possible your repro was a very unusual set of factors combined, and your more recent editing hasn't tripped the same issue yet.

In any case, the GDI object report has been proving itself effective to help us narrow such culprits down, if similar leak situation is re-discovered going forward. 

@Peter_Antal @jamieclarke Okay so today I accidentally deleted the whole folder where I would save my premiere pro projects, which is bad yeah I lost 2 or 3 days of work but apparently the problem is gone?

I've been editing for a couple hours w/o checking the GDI Objects, cause usually I only restart it when it hits around 45k and it took like 3/4 hours to hit around 40k.

After deleting my whole premiere pro projects folder I got only this in around 3 hours of work

(Premiere Pro is the 393 one) I don't know why it's apparently gone after deleting the folder where I saved all my projects from the last 6 months but I will keep working as usual and I'll see if it comes back later today.

Sorry for losing my other projects, I can still upload the media that wasn't in this folder, which are a couple copypastas' extension PNGs and I can also give you a copy of my current project that is not giving me the issue

I'm currently using the 25.0 build 61 btw

A share of repro Jamie and I indeed sounds good. Your full project isn't needed- you may find that could be a lot of media to share up.

We just need something representative to support replication the problem of the GDI leakage, as visible in the Windows task manager. The smallest timeline which still allows that is ideal to help with handling.

Hi @Pitepx - Were you able to upload that project and media to us?  Thank you for your help in troubleshooting and resolving your issue.

@Peter_Antal I can try and get a whole collect of my current project which I am pretty sure would get a crash under the default 10k quota setting - upload it to G drive and send the link to jamie, let me know if that would be of your interest so I can go forward

As we are here, can you forward this topic to some1 to see if they can gimme any update on it?

@Pitepx - Update: On Windows OS, I am currently unable to repro your GDI resource leak on playback using the project you shared to Jamie. With just the project as-is (no media) and as well with substitutions for offline files, GDI resource use was holding flat for me.

Unless @jamieclarke was able to found a trick to replicate on his end, it's looking likely there is a combination of specific formats and/or filters codepaths together with the hardware accelerated UI mode as neccessary to elicit this repro.

Jamie may have ideas on best way to deal with this kind repro'es, but for something like this I'd suggest a bare minimum "toy" project with small representative media file as ideal to replicate the leak - the full crash isn't necessary. With such a project loaded, I'd expect that when I play that content from timeline, windows task manager would track a steady rise of GDI objects from the "Details" pane, when "GDI Objects" are enabled as a column under observation.

The limit affects how much UI resources Windows OS allows application UI to use.

@Pitepx -  That adjustable limit is not a generally used feature. Microsoft recommends keeping it at default level of 10k, they haven't called out specific hazards, and do acknowledge some apps do need more, but do note it has the potential to be abused by malicious applications also.

In practice, if you saw a bunch of other apps on your machine use more GDI resources than 10k, or behaving eratically you'd probably want to consier resetting that down.

The elevated quota should not normally be needed for Premiere, and once fixed, I'd advise against leaving it relaxed where not needed.

updating status.