Hello,
In the osgcamera example I disable draw serialization like this:
Index: osgcamera.cpp
===================================================================
--- osgcamera.cpp (revision 9034)
+++ osgcamera.cpp (working copy)
@@ -204,6 +204,7 @@
while (arguments.read("-g")) {
viewer.setThreadingModel(osgViewer::Viewer::CullDrawThreadPerContext);
}
while (arguments.read("-d")) {
viewer.setThreadingModel(osgViewer::Viewer::DrawThreadPerContext); }
while (arguments.read("-c")) {
viewer.setThreadingModel(osgViewer::Viewer::CullThreadPerCameraDrawThreadPerContext);
}
+ osg::DisplaySettings::instance()->setSerializeDrawDispatch(false);
bool limitNumberOfFrames = false;
unsigned int maxFrames = 10;
I start it on a dual-core machine with the following command line:
./osgcamera -2 --CullDrawThreadPerContext cow.osg (side note: argument
parsing is wrong, -g or -c does not work)
It runs, as long as I don't bring up the stats graph, because that
causes a crash within a couple of seconds either with a segfault or
with memory corruption message, such as:
*** glibc detected *** ./osgcamera: malloc(): memory corruption
(fast): 0x00002aaab81e6c2f ***
Sometimes, but not always, preceded by a number of "Warning: detected
OpenGL error 'invalid operation' after RenderBin::draw(,)" messages.
Anybody else see this?
Are there any known caveats with disabling draw serialization?
--
Thanks,
Csaba
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
