P: Hundreds of Direct2D Drawbot error. HRESULT: -2005270494

[neilgdabc]

I'm getting hundreds of these errors, and every time they happen the UI freezes for a second or two.

Not entirely sure what build I'm running but it's 25.0. Here is the extremely useful about box:

Any ideas? Thanks!

[Dnl13]

Hey @jamieclarke,

Thanks for your response.
I’ll also reset the registry entry since I’m not entirely sure it won’t negatively impact my system in other ways.

I understand why we’re encouraged to test the beta, but a company like Adobe should be well aware that its products aren’t just for fun or hobbyists. Users shouldn’t be turned into unwilling beta testers.

This is an expensive product, not an open-source GitHub project, where one might have a different expectation of functionality and stability.

However, since I see no other way to maintain productivity for my clients without the beta, I suppose I’ll have to go that route. That said, this situation will cost at least 2 points on the infamous "Would you recommend Adobe?" question (presented in glorious Windows 95 style).

Please prioritize stable systems and only release updates once the beta versions have been thoroughly tested.

I understand Adobe is under pressure with the AI revolution, but I’d take a functioning, reliable GUI over any fancy new AI tool.

What’s the point of new features if we can’t use them properly?

I think you seriously need to rethink your release strategy.

Apologies if this comes off as less than friendly, but this issue has been ongoing for quite a while.

Filing a bug report as a regular user is nearly impossible when time seems to be the only relevant factor.

Please, please, please focus on fixes first.

Stability should come before new features (which I do appreciate, by the way).

Well then, off I go to reluctantly install the beta, hoping it won’t ruin my projects and that I’ll be able to open them in the next release.

I’m deeply concerned about the hard-fought progress I’ve made so far.

Thanks and best regards,
An unwilling beta tester

[Max291794530wtx]

@Dnl13 Could not have said it any better myself. @jamieclarke we appreciate your help so far but we would be so grateful if you could help relay this to the higherups at Adobe - we 1000% prefer a stable software over one with new tools.

[leosanab]

Tried this and it worked! Thank you

[Peter_Antal]

@Dnl13 - It sounds like you isolated a problem on this view... Can you elaborate on which views you were using for the scenario on this screenshot? A repro for this one can be a huge help, as your report on this seems to be the first on it - I have not seen anyone else comment on similar.

For more context - GDI objects are used by Windows OS to manage UI resources which applications make use of to render their UI. It gives a hard quota of them for each application to use sparingly. Premiere has used resources from this system for a long time, but two aspects changed with the 25 release:
1-The D2D system uses different OS resources in different patterns, as it employs the GPU + hardware acceleration. For a surprisingly large amount of Premiere UI, the switch between the two systems is very smooth, and has generally yielded notably better performance, but at times there have been features which implicitly relied on platform specific characteristics in abnormal ways.

2-The D2D system used for hardware accelerated UI with Premiere 25+ is much stricter about checking and enforcing that it can make use of resources. Resource allocation failures could occur in prior releases also, but there wasn't a central mechanism forcing errors to be reported in a standardized fashion.

These slow GDI leak issues discussed on this thread are challenging as they rely on local malfunctions to particular experiences, being repeatedly exercised through hundreds or even thousands of iterations. The error which gets detected is ultimately the same, but the source causing them can differ greatly. That kind of behavior can be more difficult to catch and isolate, because that type of usage isn't normally happening during normal feature integration testing, or even getting well reported via beta usage. 

As Jamie has noted where the team can reliably understand(or narrow down) what steps are leading to such failures once they are encountered, it's immensely easier to start isolating and fix the root cause.

Especially after a consistent leak repro is reported, I'd likewise recommend disabling hardware acceleration while waiting on a fix, as that path is a slower but well proven fallback.

[jamieclarke]

Hi @Dnl13 @neilgdabc  - Can you try installing Premiere Pro beta version 25.2.0 build 46 or later and let us know if you are still having issues.

[Beatriz31757337ujvd]

I have uptated to the latest version I am having this issue non stop, i cant work on  a file for more than 5 minute without this comming up, I was only adding a png to a mp4 file and it crashed with this error code.

[Beatriz31757337ujvd]

i mean on after effects

[jamieclarke]

Hi @Beatriz31757337ujvd - We need some more information to help you.  What exact version of Premiere are you using? What OS and GPU are you using?

[Peter_Antal]

@Beatriz31757337ujvd - Following on Jamie's comment, if your case was with AE, I'd recommend starting a thread for your case in the AE forum, with a title+description it in terms of your use case, with a focus on the minimal repro steps. 

AE similarly moved over to hardware accelerated UI which had been in public beta for a while, and went into release in v25.

That class of error isn't a issue for general usage of these apps, but such errors have been found to occur in particular panels/operations in connection with the move to hardware acceleration. Those error codes tells us what kind of problem arose(e.g. GPU device failure, or resource leaks), but on its own isn't enough information for folks to uniquely recognize if a bug is the same or for engineers to act on replicating and fixing such an issue.

[tmuka]

Just wanted to chime in to say this same error is affecting me too even in my simple video project.  Premiere slows down to a glitchy mess before my video drivers crash. 

[jamieclarke]

Hi @tmuka - Have you checked version 25.2 to see if it helps your issue? 

What OS are you using?  What version of Premiere?

Please share the steps to reproduce it, as this will help us investigate further.

[tmuka]

Sorry, I don't know exact steps to reproduce.  I'm just editing 2-3 minute talking head videos with some lower thirds and audio, without anything fancy or heavy.

I'm using the lastest version from Creative Cloud, Premiere 25.1.0 (build 73) on Windows 11 Pro on a new Dell XPS 16 with Intel Ultra 9 185H and RTX 4060.

I didn't have this specific issue on my 3 year old pc that was just replaced by my employer. 

I'm reluctant to install a beta version or change registry settings to resovle this as I don't want to make my system unstable as video editing is just one part of my job. 

[Dnl13]

Just to let you know:
Using the latest NVIDIA Studio driver, the latest non-beta version of Premiere, an updated Windows 10, and some cleaned-up disk space on drive C:, I was able to edit for much longer without encountering this error.

That said, I’ve only worked on smaller projects so far, mainly shorts and social media content. Still, I managed to pass the magical 1-hour mark without any issues.

Maybe it's a driver issue? 

[jamieclarke]

Hi @tmuka - Can you open Task manager and find the details pane in the Column headers, right click "Select Columns" "GDI Objects" is one of the options. Monitoring from there allows for recognizing a growing leak much earlier than when something blows up.  any steps you can reproduce to let us know when the objects start to climb would be very helpful.

[Suwan369762057z9w]

I too am getting drawbot error after updating to 25.1. I tried every solution provided by technical support but nothing worked. it really messes up the workflow especially when I am working on big projects for work.

Specs: windows 11, GeForce RTX 2070, RAM 48GB intel core i7-10th gen 

[Stan Jones]

@Suwan369762057z9w,

Are you experiencing the GDI maxing out?

https://community.adobe.com/t5/premiere-pro-bugs/p-hundreds-of-direct2d-drawbot-error-hresult-200527...

If so, you can try to avoid the UI element that is driving it. For me, it was having the Progress Dashboard open when transcribing.

Stan

[Peter_Antal]

Note:
1-This error code -2005270494 corresponds to a GPU Device not currently being available. That could be because Premiere or another app was overusing resources, or the current GPU driver has a problem. If someone hitting this one can share specific repro on how such a case is observed, that would greatly help us narrow down the culprit.

More support to handle for these error cases, describe with meaningful user errors, and better react to them is being worked on, but durable fixes (e.g. recovery mechanisms and prevention) often revolve around reliably reproducing such cases to ensure there are not related problems.

If a user consistently hits the GPU Device error of -2005270494 , I'd recommend trying with UI GPU acceleration disabled in near term + sharing a minimal repro.

2-@tmuka - The "Invalid Image File" issue is likely some kind of problem with an image provided by the application (e.g. for some UI content) or somehow in your project. Please spin up a dedicated thread on that, and loop me in on it. I would expect that sort of thing should have a pretty simple repro(e.g. showing some UI or making use of some imported content).

3- To @Stan Jones 's case of GDI resources leak - The Progress dashboard indeed had a GDI resource leak affecting a range of audio-processing scenarios. The fix for that is present in the Beta builds, and will be present in the next release version. 

Disabling GPU UI acceleration should work as a general mitigation or avoiding repro on the progress dashboard are mitigations in meantime.

If someone observes a GDI leak which doesn't involve the Progress dashboard, please start a separate thread, share repro context and loop me in.

[Rach McIntire]

Updating bug status

[Guest]

[Carlos Ziade]

Reset Preferences

Clean Media Cache

Delete Render Files

[Peru Bob]

If the suggestions by Carlos Ziade don't work,
If that doesn't work, try creating a new project and import the old one into it.

[jamieclarke]

Hi @Deleted User - Please see pinned post

[Dnl13]

Additional observations that seem to lead to the issue:

Version: 25.1.0 Build 73

This is not a GDI issue! I was able to monitor two sessions in a row and identified a GDI peak of just 181 objects. However, you're leaking memory in the dedicated GPU memory—approximately 700k per tick during normal timeline playback.

Key observations:

1. Memory never clears unless focus shifts to another window (e.g., Chrome). Switching back to the Premiere window immediately refills both regular memory and dedicated GPU memory.
2. If the system is further stressed (e.g., simultaneous playback and an Ollama model loaded in GPU memory, LLM with 5GB), the issue triggers even below 2GB of GPU memory usage.
3. The program lacks an effective memory manager or garbage collector for GPU memory. The GPU memory usage grows indefinitely until rendering errors occur.

Disabling GPU acceleration for the timeline is not an option on my system:

• The entire application becomes laggy and unresponsive.
• This "solution" makes Premiere entirely unusable for longer projects.

Editing short clips is manageable, but working on longer films is frustratingly impractical.

Please prioritize addressing this critical issue, as this software—at its current state—feels like a defective product. Installing the beta is not a viable workaround for me.

And you should hurry! With the new EU regulations, you are now liable for software defects, and in my view, this qualifies as a warranty case. I also hope that my country will swiftly implement this EU directive.

[Moto--]

Been getting a lot of bugs lately, When using Dynamic Link with PR and AE when I'm switching to PR to edit while leaving AE open without touching anything suddenly AE Sucks up all of my ram, EVEN the dynamic link Clip was disabled. Needed to restart AE ALL OF THE TIME just to solve the problem. Also been getting this post problem the UI FREEZES and everything stops. IT crashes both PR and AE at the same time. 

25.1 version makes it even worse A LOT OF BUGS. Transform effect won't even display real-time to the preview. It's jumping frames. 

PC SPEC:
- 32 GB RAM
- RTX 4060 GPU
- 10 the gen i5

[Peter_Antal]

Thanks for highlighting the context of your cases @Moto-- & @Dnl13  .

Can you share minimal workflows to highlight problem scenario of resource leak you've observed there?

(not neccessarily culminating to the crash, but a repeatable operation showing a steady growth pattern which doesn't stabilize when operation is completed)
Thanks