Never mind, I forwarded an old message! :)
From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf
Of Gianluca Natale
Sent: Monday, October 23, 2017 12:34 PM
To: Osg Users <osg-us...@openscenegraph.org>
Subject: [osg-users] FW: found memory leak in OSG 3.0.1
Hi all,
Hi Gianlica,
Personally I wouldn't worry about this tiny one off "apparent" leak.
It could well be just an artefact of the way the memory tracking is
working rather than a real leak, from what I pick up from other
Windows discussions here on osg-users the MS memory is known for not
tracking
h Users <osg-users@lists.openscenegraph.org>
Subject: Re: [osg-users] found memory leak in OSG 3.0.1
Hi Gianluca,
How you are measuring the memory usage? It could simply be that the memory
tracking isn't properly handling deallocations.
As a general note, close will just close the gr
Hi Gianluca,
How you are measuring the memory usage? It could simply be that the
memory tracking isn't properly handling deallocations.
As a general note, close will just close the graphics context, it
won't delete the osg::GraphicsWindowWin32. Try testing the creation
of a viewer within a
Hi all,
In my application I'm using OSG 3.0.1 (I do know it is old, but I do not have
the time now to move to a newer version).
I think I have a memory leak, and I don't know if it's my fault or a bug in OSG.
Using the task manager (on Win 8.1 Pro), I see this.
When I call:
GraphicsContext*
5 matches
Mail list logo