Annoying error messages at init

duburcqa · April 11, 2021, 11:01pm

Hi,

I’m running a ShowBase in Python with the following configuration:

framebuffer-software 0
framebuffer-hardware 0
load-display pandagl
aux-display p3headlessgl
aux-display pandadx9
aux-display pandadx8
aux-display p3tinydisplay
notify-level fatal

I get this error messages before actually falling back to p3tinydisplay successfully:

Attempt to register type x11GraphicsPipe more than once!
Attempt to register type x11GraphicsWindow more than once!

Is it possible to get rid of them ?

Apparently those error messages are sent to std::err systematically without any mechanism to avoid it:

github.com

panda3d/panda3d/blob/eb367430f7d4aad7d01e5b9212534b066e5a21f6/dtool/src/dtoolbase/typeRegistry.cxx#L102


  // time, but now it's different!  Bad juju.
  cerr << "Reregistering " << name << "\n";
  type_handle = rnode->_handle;
  _lock.unlock();
  return false;
}

if (type_handle != rnode->_handle) {
  // Hmm, we seem to have a contradictory type registration!
  cerr
    << "Attempt to register type " << name << " more than once!\n";

  // This is invalid, but we'll allow it anyway.  It seems to happen for
  // some reason under GNU libc5 that we occasionally end up with two
  // legitimate copies of the same class object in memory--each with its own
  // static _type_handle member.

  type_handle = rnode->_handle;
}
_lock.unlock();
return false;

I guess redirecting std err to /dev/null completely is not an option if I still want to get fatal error messages ?

Thank you in advance.

rdb · April 12, 2021, 1:41pm

It’s a consequence of a lack of architectural separation between the windowing and display code, causing some classes to be loaded twice. Fixing that will require solving this issue.

Specifically, the problem occurs when pandagl and p3tinydisplay are both loaded into memory.

However, I’m open to thinking about some workaround for this.

duburcqa · April 12, 2021, 2:21pm

Yes that’s what I guessed. It is not a big deal in practice, so it is fine like this. I just wanted to make sure I didn’t miss something Thank you anyway !