[osg-users] Profiler with OSG
vincent.bourdier at gmail.com
Fri Sep 19 06:31:12 PDT 2008
@Sergey : I currently do it, but it returns me a lot of leak, and a lot
looks like false positive...
Thanks Jean-Sébastien for AQTime ans gDebugger, I'll have a look at these.
Thibault, thanks a lot for this very detailed answer. I think I will find my
problems with all these possibilities.
Thanks a lot, I'll tell you if I find an easy solution to find memory leaks.
2008/9/19 Jean-Sébastien Guay <jean-sebastien.guay at cm-labs.com>
> Hi Vincent,
> No one never profile his OSG code ?
> I think everyone has different ways of working. I tend to evaluate
> performance with the Stats Handler and try out different variations of
> algorithms to see which one performs better. I've rarely needed to do actual
> When I did need to, I've used AQTime and gDebugger for general and OpenGL
> profiling respectively. Neither is free though.
> Apparently if you're on Linux you can use valgrind to find memory leaks
> (and I hear that either it understands ref_ptr natively or there's a
> workaround to eliminate the related false positives) and oprofile to profile
> your code. I don't work on Linux enough to have had to use them myself
> Sorry I can't help more,
> Jean-Sebastien Guay jean-sebastien.guay at cm-labs.com
> osg-users mailing list
> osg-users at lists.openscenegraph.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osg-users