Skip to main content
Participating Frequently
December 17, 2021
Question

BUG REPORT: OpenGL failed during render, returns "Creative Cloud not found", requires re-install

  • December 17, 2021
  • 1 reply
  • 246 views

I've encountered this a few times during rendering - Media Encoder freezes, memory usage of CA Beta goes to around 8 GB, and eventually Media Encoder returns an error box "OpenGL failed. Creative Cloud is required to resolve this but is missing."

To begin with, CC is NOT missing. The current software doesn't allow using any of the software unless you are logged in to the Adobe servers, and CC is always auto-updating (which is another annoyance - CC will update in the middle of a render or complicated recording/rigging and shut down or slow/glitch the process. It would be extraordinarily useful to either be able to use the software without being logged in for a few days or the duration of a project, or else certain implementations should code for a process halt in CC). 

But I digress. The OpenGL failure requires a shutdown of all Adobe software while CC completely reinstalls itself. But that is a manual acceptance of the error return - I set a render to run last night and it should have taken about an hour, but I walkde in this morning to the error message waiting for acceptance to repair or reinstall CC. 

This topic has been closed for replies.

1 reply

Participating Frequently
December 17, 2021

ADDENDUM - so this has happened four times in a row now; ME is unable to complete the render. I'm writing a .mov file with an alpha channel, although this also occurs with a regular export. A set of PNG files with WAV appears to function okay, but then I am left without the alpha channel. I can't see the code, of course, but the time remaining slowly increases as the render proceeds, so I am assuming there is a memory leak somewhere, in which (maybe) a frame is completed and should be written to file but is also written back to the queue. 

CoSA_DaveS
Adobe Employee
Adobe Employee
December 18, 2021

Can you share a screen shot of the error message? What are the version numbers for your OS, Ch, and AME?

 

> A set of PNG files with WAV appears to function okay, but then I am left without the alpha channel.

Actually those PNG files do have an alpha channel, so that should at least give you a way to keep working. But we'd still like to solve the root problem.

 

Ch using more memory when AME is frozen is probably because it has frames in the queue (stored in memory, not on disk) that have to stick around until AME is ready... which it never is because it's frozen.

Participating Frequently
December 20, 2021

Thanks for the reply! 🙂

 

I can't reproduce the specific error message dialog without going through the freeze process, and when it appears, things are frozen and no screen shot possible. 

 

But - 

 

OS: Windows 10 P

CA Beta - V. 22.2 Build 18

AME Beta - V. 22.2 Build 9

 

I did indeed see that the PNG files have an alpha channel, which saved my bacon this time around. I'll see if I can figure out a way to get a screen shot of the error process and the Performance tab in Task Manager