Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1633734414.1208006143526.JavaMail.jira@brutus>
Date: Sat, 12 Apr 2008 06:15:43 -0700 (PDT)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Closed: (AMQCPP-173) C++ Client has memory leaks
In-Reply-To: <120649865.1207586792630.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQCPP-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQCPP-173.
-------------------------------

      Assignee: Timothy Bish  (was: Nathan Mittler)
    Resolution: Cannot Reproduce

The data provided by the MSVC memory detector is not really sufficient to determine if any of these are really leaks.  Running the code through valgrind on unix platforms shows no leaks.  Given the mass restructuring done in V2.2 I'm closing this issue.  If we can get access to a real windows memory leak testing tool such as Rational Purify and find issues we can reopen or create a new issue.  

> C++ Client has memory leaks
> ---------------------------
>
>                 Key: AMQCPP-173
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-173
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.1.3
>         Environment: Visual Studio 2008, Windows XP Pro SP2
>            Reporter: John Urberg
>            Assignee: Timothy Bish
>             Fix For: 2.2
>
>         Attachments: dump.txt
>
>
> I added memory debugging calls to the vs2005-activemq-example project.  When I ran it it produced a memory leak dump.  To recreate, do the following:
> 1) Add the following to the top of main.cpp:
> #define CRTDBG_MAP_ALLOC
> #include <stdlib.h>
> #include <crtdbg.h>
> 2) Add the following to the bottom of the main function:
> _CrtDumpMemoryLeaks();
> 3) Run the application thru the debbugger
> The output will display a memory leak dump similar to the one attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.