Ramanjaneyulu malisetti wrote:
Hi Alberto,
Yes I do. I read in forums that there are many
memory leaks fixed after 2.6.0. Are they related to this scenario.
If you could point us to these forums, it would help. It doesn't do much
good for people to post in forums that there are memory leaks, but not
report them in our bug database.
I did diff of 2.6 and 2.8 source code. I see at many places memory is
alloced and dealloced through fMemoryManager.
Unless you use the pluggable memory management in a particular way, these
changes will not affect you. Also, many of the leaks that were plugged
occur only when exceptions are thrown in certain circumstances, so you are
unlikely to encounter them. It would not make much sense for you to
back-port all of these changes to your code, especially if you're worried
about moving to the latest release.
If this can address this issue. Merging relavent sections of code from
2.8 to 2.6 make sense?
You should first attempt to diagnose the leaks through Purify to see if
there is already a fix in 2.8 or 3.0. If there is, you can back-port the
change to 2.6.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
