Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 75697 invoked from network); 9 Dec 2010 14:36:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Dec 2010 14:36:54 -0000 Received: (qmail 5527 invoked by uid 500); 9 Dec 2010 14:36:54 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 5370 invoked by uid 500); 9 Dec 2010 14:36:54 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 5362 invoked by uid 99); 9 Dec 2010 14:36:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 14:36:53 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of glahiru@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 14:36:46 +0000 Received: by eyf18 with SMTP id 18so1547296eyf.39 for ; Thu, 09 Dec 2010 06:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=4G/BElJWk6DyP3oldPDxQjsarYvogF+0px8hNo/GpUk=; b=c+xcJVW39d1s/e/BY4J7GKfSwx+4oL3nhmAdTMhesaouU1QMEzBvNUoFAAtqC2r7EA gANBr2yNvCVqw+300s0S7Sge2jWNFQdRMuK+J8qhggvEUmclRGwE412DomvrkmHyUI5O qs2Xx1HyGaVS/laPAPk5owzVzYzyxNnu38jEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=etXaTH15B6XGP++2/H5jMSWTW0wRcQn4olsoLLAfjzOHwVjXAhNbjomAxHKKmkACqN Hu0ipoi/9sY1sbU9/mjsrk5rczKQM7ZoxP2qAziqE94ONo4EmimRJY/skcbWahAC2Jdu TIdLYlqBOgb5nKxDazfurF9tUDRIUjw0k0aM4= MIME-Version: 1.0 Received: by 10.216.3.3 with SMTP id 3mr641751weg.57.1291905386429; Thu, 09 Dec 2010 06:36:26 -0800 (PST) Received: by 10.216.71.149 with HTTP; Thu, 9 Dec 2010 06:36:26 -0800 (PST) In-Reply-To: References: Date: Thu, 9 Dec 2010 20:06:26 +0530 Message-ID: Subject: Re: qpid C++ memory leak From: Lahiru Gunathilake To: users@qpid.apache.org Cc: "Faruqui, Faisal" , "Ramalingam, Saravanan" , "Kuo, Jennshi" , "Harpalani, Manish" Content-Type: multipart/alternative; boundary=0016364d265ba43fba0496fb29d0 X-Virus-Checked: Checked by ClamAV on apache.org --0016364d265ba43fba0496fb29d0 Content-Type: text/plain; charset=ISO-8859-1 Hi Dennis, As far as I can see you are simply sending large number of messages to Qpid Java broker but not consuming any of the messages. So obviously memory will grow unless you consume those messages since you are running without persistent storage. I recently did stress test with Qpid C++ broker with large messages up to 5MB and I couldn't find memory leaks with valgrind. Hope this helps ! Regards Lahiru On Thu, Dec 9, 2010 at 4:09 AM, Qin, Dennis wrote: > Hi All, > > I have downloaded the Linux version of qpid C++ broker 0.8 on my Linux > appliance. I ran some stress tests on this broker server and found memory > leaks. Here is the simple test I did. > > > 1. Launch the C++ broker using the following CLI, > > ./src/qpid --daemon > > 2. Launch the server program under the examples/request-response > directory, > > 3. Create a shell script to send client messages constantly to the > server under the examples/request-response directory , here is my script, > > > > #!/bin/bash > > > > while true > > do > > ./client > > done > > > > and launch this script > > > > 4. Check the C++ broker memory usage using ps auxf and pmap. > > > > It shows memory usage constantly increasing as the script running to send > the message. > > > > Looks to me there are somewhere inside the broker code that keeps > allocating the memory and not releasing it. > > > > Any idea if this issue has already been reported and will be fixed in the > next release? > > > 5. Here is my appliance Linux version, > > 2.6.18-92.1.6.el5PAE #1 SMP Wed Jun 25 14:21:46 EDT 2008 i686 > i686 i386 GNU/Linux > > > > Thanks. > > > > Regards, > > > > Dennis Qin > > > > --0016364d265ba43fba0496fb29d0--