Re: Memory leaks in Orbacus
Dion Picco <[email protected]> Mon, 20 Jun 2005 12:46:45 -0230
| Newsgroups | gmane.comp.corba.orbacus |
|---|---|
| Organization | IONA | Making Software Work Together TM |
| Message-ID | <[email protected]> |
Hi Andrey, On Mon, Jun 20, 2005 at 05:48:19PM +0400, Andrey Mikhalchuk wrote: > Hi Dion, > > Thank you for the patch - I'm currently discussing it with my colleagues. > Could you please let me know which particular problems this patch fixes? > > I also have a question about the memory leaks - how do you verify that > Orbacus doesn't have memory leaks? Do you use some profiling tool? What is > the coverage of the test suite used for the memory leaks checking in 4.2.2? > > Thanks, > Andrey Mikhalchuk The patch fixes a few issues: 1) Possible segfault was fixed in the connection handler on the client-side 2) Improved concurrency with the Leader-Follower model 3) 64-bit warnings during compilation were fixed 4) Fixed a deadlock in a COMM_FAILURE exception circumstance 5) General optimizations As far as profiling goes we use both Rational Purify as well as Valgrind on Linux. We test various demos and tests that ship with Orbacus as well as some extra stress-tests that we have designed to simulate high-load conditions. I'd recommend applying this patch to your version of Orbacus... it should only improve on existing functionality and will perhaps save you time on future support issues. Cheers. -- Dion Picco, Software Engineer IONA Technologies Inc. Team Orbacus - Your CORBA Source mailto:[email protected] http://www.orbacus.com _______________________________________________ OB-Users Mailing List - [email protected] http://mail.ooc.nf.ca/mailman/listinfo/ob-users Visit our support FAQ before you send a message. http://www.orbacus.com/faq/support.html