[
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: [email protected]
For additional commands, e-mail: [email protected]
