Hi Andy, You can enable the "Thread Count" column in Windows Task Manager from its View->Select Columns menu.
Regards, Can. On 9/19/06, Andy Preece <[EMAIL PROTECTED]> wrote:
Hi, > This is related with MFC runtimes and threading mechanism. I guess that in DEBUG mode OpenThreads can not be finalized etc. So the error messages are coming from the OpenThreads library? > But again dont worry, because we are sure that there is no memory leak. It is tested with some programs (rational etc.) and there is no memory problem... I am not worried about a memory leak, but it is hard to track down other issues I have (i.e. crashing on exit for other reasons) with all that debug printing out. > Instead of file->exit option, directly press the stop button on visualstudio. In release mode or in your final production you can use file->exit without any problem That seems to be the case (with the exception being I still have another bug somewhere else :-)). I am using a simple, single Producer::RenderSurface with an osgUtil::SceneView (as in OSGMFC). How many threads will this produce in OSG? (i.e. will I have a separate thread for draw, cull and app?) How do I find out how many threads I have running in my Windows app? Regards, Andy. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mustafa Sent: 19 September 2006 11:00 To: osg users Subject: Re: [osg-users] OSG debug with VS 2005 Hi Andy, Dont wory about these messages. In release mode you will not see any error or memory dump messages after exiting your application. Briefly, in DEBUG mode lots of messages, in RELEASE mode nothing... This is related with MFC runtimes and threading mechanism. I guess that in DEBUG mode OpenThreads can not be finalized etc. But again dont worry, because we are sure that there is no memory leak. It is tested with some programs (rational etc.) and there is no memory problem... Instead of file->exit option, directly press the stop button on visualstudio. In release mode or in your final production you can use file->exit without any problem BR 2006/9/19, Robert Osfield <[EMAIL PROTECTED]>: > Hi Andy, > > Try running your app in a console and catch all the messages, redirectling > to a file. I'm not sure how to do this under Windows, but I wouldn't have > thought there would be a way of doing it. This is what I do under unices. > > osgviewer cow.osg &> output.txt > > This catches all error messages. If you had cygwin installed the above > would work as well. > > The OSG has its own message system, they you can control the verbosity of > using the OSG_NOTIFY_LEVEL env var, set this to ALWAYS and it'll always eat > all messages, set it to NOTICE and it'll only print out important > messagages, set to INFO and it'll lots of info about what its doing, and > finally DEBUG to print out debug information as well. > > You can also set the notification level using > osg::setNotifyLevel(osg::INFO); > > As the cause of the particular problem I have no clue, as I'm not even sure > what problem you are reporting. > > Robert. > > > > On 9/19/06, Andy Preece <[EMAIL PROTECTED]> wrote: > > > > > > > Hi All, > > > > I am working with OSG 1.1 and MS VS 2005. In the IDE I can switch between > debug and release builds. I am working with the OSGMFC example program. > > > > When I compile and run with a debug build and I exit the program (using the > File -> Exit menu option) I get a mass of messages printed out in the > Immediate Window. The messages scroll by so fast it is difficult to read > them, but they look like they might be debug information from inside OSG as > they mention 'normal data' and 'color data'. > > > > I have searched through the OSG src code but can not find any obvious > candidates. > > > > Anyone know what these messages might be? How can I stop them coming out (as > they are a real pain when trying to find other bugs)? > > > > Regards, > > Andy. > ________________________________________________________________________ > This e-mail has been scanned for all viruses by Star.The service is powered > by MessageLabs. > ________________________________________________________________________ > > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > > _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ ________________________________________________________________________ This e-mail has been scanned for all viruses by Star.The service is powered by MessageLabs. ________________________________________________________________________ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
