It sounds questions about memory leak reports on Windows come up often.
I'd like to address this in the FAQ. Any objections?
Cory
Robert Osfield wrote:
Hi Adrian,
In the early days of the OSG I wrote a few custom new/delete operators
and the associated infrastructure for tracking memory,
Hi Adrian,
In the early days of the OSG I wrote a few custom new/delete operators
and the associated infrastructure for tracking memory, but in the end
it was too painful to maintain and really not anything to do with the
core OSG's focus. There are far better tools out there for tracking
memory
Adrian-
For the record, I made my posting because I thought other Windows
developers would like to know the source of at least some of the false
positives. I wasn't claiming to have found a real leak.
Cory
Adrian Egli OpenSceneGraph (3D) wrote:
Hi Robert,
Since i am member of the osg-use
Hi Robert,
Since i am member of the osg-user mailing list, we get each month a least
one guy asking the community about the problem of memory leak in OSG core.
The problem is simply to say, that the most of them are working
with 3rd party tools like bound checkers and they trust them. Of course th
4 matches
Mail list logo
