Hi J-S,
Jean-Sébastien Guay wrote:
I am currently chasing memory leaks in our application, which is like
a modeling tool where the user will open/work on/save/close data files
multiple times during the same application run. What we are seeing is
that when a file is closed, not all memory
Hi Jean-Sébastien,
Jean-Sébastien Guay schrieb:
However, running IBM Purify on the application reveals no massive leaks,
only a few false positives. Are there any tools or techniques that
someone could recommend to make finding and fixing memory leaks easy,
and which work well with OSG? I
Paul Melis wrote:
Hi J-S,
Jean-Sébastien Guay wrote:
I am currently chasing memory leaks in our application, which is like
a modeling tool where the user will open/work on/save/close data
files multiple times during the same application run. What we are
seeing is that when a file is closed,
2008/12/19 Pierre Bourdin (gmail) pierre.bour...@imerir.com:
Hi,
valgrind is very powerfull if you're on an Linux/Unix environnement, if you
are using MSVC you can use this:
add this bloc at the beginning of each file you want to trace (after all
includes):
#ifdef _WIN32
# ifdef _MSC_VER
Le vendredi 19 décembre 2008 à 13:43 +, Simon Hammett a écrit :
2008/12/19 Pierre Bourdin (gmail) pierre.bour...@imerir.com:
Hi,
valgrind is very powerfull if you're on an Linux/Unix environnement, if you
are using MSVC you can use this:
add this bloc at the beginning of each file
Hey guys,
Stephan Huber wrote:
However, running IBM Purify on the application reveals no massive leaks,
only a few false positives. Are there any tools or techniques that
someone could recommend to make finding and fixing memory leaks easy,
and which work well with OSG? I tried Visual Leak
Hello Pierre,
valgrind is very powerfull if you're on an Linux/Unix environnement, if
you are using MSVC you can use this:
...
when you stop debugging you program, it make a memory leaks report in
the msvc output console...
Does this work well with ref_ptrs? i.e. will it spit out hundreds
Paul Melis wrote:
Hey guys,
Stephan Huber wrote:
However, running IBM Purify on the application reveals no massive
leaks,
only a few false positives. Are there any tools or techniques that
someone could recommend to make finding and fixing memory leaks easy,
and which work well with OSG? I
Hi Stephan,
If you are interested in the code (it's integrated with other code, but
the principle should be clear) drop me a line.
Yes, I am very interested. You mentioned circular references, and this
is my current area of focus - does your code help finding these? For
example, a node
Hi Paul,
Good sleuthing, I'll try your code out and see if I can improve on it a
bit too...
In J-S's original simple test case I get around 250 Referenced instances
that are never deallocated when stopping at breakpoint 2, but sadly
can't tell where they come from. Perhaps moving
Le vendredi 19 décembre 2008 à 10:31 -0500, Jean-Sébastien Guay a
écrit :
Hello Pierre,
valgrind is very powerfull if you're on an Linux/Unix environnement, if
you are using MSVC you can use this:
...
when you stop debugging you program, it make a memory leaks report in
the msvc
Hello all,
I am currently chasing memory leaks in our application, which is like a
modeling tool where the user will open/work on/save/close data files
multiple times during the same application run. What we are seeing is
that when a file is closed, not all memory related to scene graph
Hi Jean Sebastion,
If your application run on linux plateform you can try valgrind, it will
give you a lot of informations about leaks and more.
Cheers,
Cedric
Jean-Sébastien Guay wrote:
Hello all,
I am currently chasing memory leaks in our application, which is like
a modeling tool where
13 matches
Mail list logo
