Re: [PyOpenGL-Users] PyOpenGL/PySide QML interaction bug

[Mike C. F. <mcf...@vr...>]

On 11-05-09 11:35 AM, Henry Gomersall wrote:
...
> Is this a bug with primarily PyOpenGL or should I be getting on to
> PySide? Clearly PyOpenGL should handle imports and dependencies without
> breakages.
I don't see the bug(s) with an Kubuntu Natty (11.04), Radeon HD 3650
(with the FireGL bindings).  PyOpenGL doesn't have any internal
threading operations, so the most likely culprit would be something in
PySide keeping the rendering loop running.  Other possible culprits
might be code which is attempting to do cleanup that crashes when the
references to GL or numpy go to None during interpreter shutdown; a
raised exception may be preventing the finalization/destruction of the
context.  That might be in PyOpenGL or elsewhere, but I can't readily
track it down without some traceback or the like.  I suppose it would be
possible that something is doing reference counting for the windows and
winding up with a loop due to something being held by PyOpenGL, but that
seems unlikely given the symptoms.

We're likely looking at something low-level, as differences in
hardware/drivers are causing the error to appear/disappear, but I don't
see anything obviously wrong with what you're doing.  I don't have any
machines updated to 11.11 yet, so we might possibly be looking at an
11.11 regression, or a bug in the r600 driver?  If it's easy for you,
can you test with the FireGL (proprietary) driver or an 11.04 machine?

Good luck,
Mike

-- 
________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com