AE error, Droverlord?

[Atomic]

It’s actually Dr. Overlord, kind of like NT’s Dr. Watson I presume.

[Harrybo]

Yep! This has started happening to me too!

I really cannot find any information on a: what it is and b: how to stop it from happening!!

Grr!!

[Jonas Bendsen]

Just got the same thing working in Premiere CS4.1, but it brought up a Windows Taskbar Tab that said “DroverLord – TabPanel Window” and then froze and crashed.

WTF?

I thought it was some sort of malware or virus, but this is a clean (legitimate) version of Adobe Creative Suite Production Premium 4 and I’ve run several anti-virus and malware sweeps and nothing was found.

:::::::::::::::::::::
This is my life, I edit and edit and edit and edit…

[Roy Messinger]

It just happened to me to…
ANy ideas, someone?
It happenned to me at PPRO.
Roy

[Jonas Bendsen]

The response I received from Adobe over at their boards was basically “don’t worry about it.” Pretty great, huh?

[eye roll]

The error is basically left over from testing before release, and while “Droverlord” sounds incredible menacing, it’s just a name they gave a common error for quick identifying.

:::::::::::::::::::::
This is my life, I edit and edit and edit and edit…

[Martin Guillemette]

I have same error message in Premiere CS5, only when I use Pixeland transitions on pics.

[Wolf Lawrence]

my droverland crash came with multiple oddities in parallel:

+ apps like task mgr stopped responding
+ i saw a neatvideo plugin error log itself in popup cmd window
+ i saw multiple Pr processes running in task mgr each claiming 800-900MB of memory

the droverland crash was the best early warning alert that ppcc cant handle native .mts editing as well as adobe purports it can; once i started adding basic video effects i.e. color correction, matching, motion fx, plugins, etc, these choked the .mts project.