You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Darryl L. Pierce (JIRA)" <ji...@apache.org> on 2012/12/06 19:29:09 UTC
[jira] [Commented] (QPID-4493) Memory leak in perl bindings?
[ https://issues.apache.org/jira/browse/QPID-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511591#comment-13511591 ]
Darryl L. Pierce commented on QPID-4493:
----------------------------------------
I found the problem exists even without the larger capacity: it just takes a lot longer to show up. I ran the above setup but without setting the capacity and found that, after 2.5 hours, memory had leaked to 2.8% of available in Perl.
Talking with someone else here who mentioned a similar memory leak in Perl bindings generated in Swig. He's getting me some details for how they diagnosed the problem and hopefully that will lend itself to the solution.
> Memory leak in perl bindings?
> -----------------------------
>
> Key: QPID-4493
> URL: https://issues.apache.org/jira/browse/QPID-4493
> Project: Qpid
> Issue Type: Bug
> Affects Versions: 0.18, 0.20
> Environment: RHEL5, RHEL6
> Reporter: Jimmy Jones
> Assignee: Darryl L. Pierce
> Attachments: drain.pl, map_sender.pl
>
>
> I've been having problems with long running code using the perl bindings leaking memory, specifically after calls to getProperties and decodeMap.
> To reproduce - edit drain.pl to call {{$receiver->setCapacity(100)}} and then run {{drain.pl -f amq.match}}. You'll also need to hack map_sender.pl to send to amq.match and loop forever (both attached). The memory usage of drain.pl will now start growing...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: [jira] [Commented] (QPID-4493) Memory leak in perl bindings?
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
On Sat, Dec 15, 2012 at 04:56:37AM -0800, Paul wrote:
> Hi,
>
> I have been doing some testing with the Python interface using the SWIG
> generated cqpid library. I also see a memory leak when accessing the
> getProperties method. I haven't tried the decodeMap method so dont know
> whether this was causing a problem in Python. I am using version 0.18. It
> looks like it might be related to the Perl issue and therefore would be
> grateful if you could keep me informed of the solution.
Thanks for the additional information on this, Paul. I'm looking into
the problem and will focus more on the getProperties binding in Perl.
If you want to follow the status on this, add yourself to the JIRA [1]
so you'll see updates as they're posted against the issue.
[1] https://issues.apache.org/jira/browse/QPID-4493
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
Re: [jira] [Commented] (QPID-4493) Memory leak in perl bindings?
Posted by Paul <pa...@virginmedia.com>.
Hi,
I have been doing some testing with the Python interface using the SWIG
generated cqpid library. I also see a memory leak when accessing the
getProperties method. I haven't tried the decodeMap method so dont know
whether this was causing a problem in Python. I am using version 0.18. It
looks like it might be related to the Perl issue and therefore would be
grateful if you could keep me informed of the solution.
Cheers
Paaul
--
View this message in context: http://qpid.2158936.n2.nabble.com/jira-Commented-QPID-4493-Memory-leak-in-perl-bindings-tp7585857p7586293.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org