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]

Thank you so much for this great explanation! I’ve now changed the registry entry and will keep an eye on whether it improves things.

Normally, I’m not a big fan of advice I can’t fully understand—especially since I have no idea what these GDI Objects actually are (they sound like graphical elements 😉 ). I’m also not too keen on tinkering with the registry, but given the urgency of the situation, it seems like this is the way to go for now.

Thanks again for your quick response; I really appreciate it!

I really hope that a hotfix will be released soon, or that part of the beta can be made available as a stable version. Otherwise, I’m concerned that the registry change might negatively impact other processes. Fingers crossed!

Thanks again! 

The elements marked in red here are triggering an error, while the green ones are not.

 With each mouseover, I can reveal or hide GUI elements, and an error is triggered.

[Dnl13]

Hello @Max291794530wtx,

Unfortunately, I have to let you know that this didn’t work for me. I followed your instructions, changed the key, and restarted the PC.

The error occurred again after about an hour. However, I’ll leave the registry entry as it is for now since I got the impression that the overall UI felt a bit snappier and more responsive.

Thank you so much for trying to help me!
Best regards!

[jamieclarke]

Hi @Dnl13 - I would not expect that changing the registry would help your situation.  It will most likely just delay the memory leak. We ask users to check the beta version because there are updates and bug fixes that we find after a version has released.  You are running into one of those issues which is a memory leak within the GDI objects section.  We believe we have addressed this in the next version of Premiere, but we ask you to try the beta just to be sure we didn't miss anything.  Thank you for your detailed information especially the controls that is causing this for you.  Please install the beta and let us know if it helps your issue.

[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.

[Leonel98A4]

Tried this and it worked! Thank you