qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darryl L. Pierce (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5535) Memory leak in Perl bindings when fetch() called with duration
Date Fri, 13 Jun 2014 13:28:01 GMT

    [ https://issues.apache.org/jira/browse/QPID-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030611#comment-14030611
] 

Darryl L. Pierce commented on QPID-5535:
----------------------------------------

So, with my initial testing:

 1. created queue "my-queue" on qpidd
 2. ran the Perl spout.pl with : "spout.pl -c 1000000 my-queue"
 3. modified the drain_duration.pl to connect to "my-queue"

I see the qpidd (broker) process using currently 25.7% memory, but Perl itself isn't showing
up in to when sorted by memory consumption. And when looking with qpid-stat I see:

{code}
Queues
  queue                                     dur  autoDel  excl  msg    msgIn  msgOut  bytes
 bytesIn  bytesOut  cons  bind
  ==========================================================================================================================
  82dfd6c8-dbbd-4a72-84e3-66db5692c9a5:0.0       Y        Y        0      0      0       0
     0        0         1     2
  my-test                                                       1.17m  4.16m  2.99m   51.5m
  183m     131m        1     1
{code}

Is there something additional I need to do to produce this error?

> Memory leak in Perl bindings when fetch() called with duration
> --------------------------------------------------------------
>
>                 Key: QPID-5535
>                 URL: https://issues.apache.org/jira/browse/QPID-5535
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, Perl Client
>    Affects Versions: 0.24
>         Environment: RHEL6/2.6.32-220.13.1.el6.x86_64 swig-1.3.40-6.el6
>            Reporter: Hazel Bobrins
>            Assignee: Darryl L. Pierce
>         Attachments: drain_duration.pl
>
>
> When fetch() is called with a duration and no messages exist memory is leaked
> How to reproduce
> Create a queue
> Run attached code example
> Watch memory stats
> Example memory stats while running the above
> time,VmPeak,VmSize,VmHWM,VmRSS,VmData,VmStk
> 1391425166,236444,210368,15164,15164,81772,88
> 1391425171,236444,212212,16960,16960,83616,88
> 1391425176,236444,213928,18764,18764,85332,88
> 1391425181,236444,215764,20560,20560,87168,88
> 1391425186,236444,217608,22360,22360,89012,88
> 1391425191,236444,219324,24176,24176,90728,88
> 1391425196,236444,221172,25972,25972,92576,88
> 1391425201,236444,223016,27768,27768,94420,88
> 1391425206,236444,224732,29556,29556,96136,88
> Memory does not seem to be leaked if there are messages waiting on the queue or if no
duration is provided and messages are present on the queue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message