Hi Antonie,

On Dec 18, 2007 8:55 PM, Antoine Hue <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Before stating the issue we have, please let us thank you very much for
> OSG 2.2. Quality is continuously improving in OSG.

Thankyou, we strive... don't always get a perfect 10.0, but we do at
least try...

> We have moved our app to this version, 2.2.0. We are now using
> osgViewer::Viewer wrapped into a QT 4 Widget as in osgviewerQT.
> We currently have a crash on application exit under Mac OS X.
>
> Everything goes OK until the osgViewer:Viewer is destroyed. System stack
> trace is pasted below.
>
> Are there any other report of such thing ?

Yes... more below...

> Could it be that destructor is not called at the right time during the
> update cycle ?

The destructor is fine, what is up is that with some set ups such as
GraphicsWindowEmbedded, or certain other combinations of windowing
destruction order the makeCurrent() fails and the subsequent flush of
OpenGL objects in the scene graph to for the OSG to clean up properly
fails as you can't call OpenGL without a valid graphics context
obviously.

The fix is to do a check in the GraphicsContext::close() method to see
if the makeCurrent() worked, i.e. returned true, and only do the flush
of OpenGL objects if this sucedded.  The fix is checked into OSG
SVN/OSG2.3.0.

So... OSG quality does continue to improve ;-)

Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to