[
https://issues.apache.org/jira/browse/PROTON-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605933#comment-16605933
]
Christoph Scheiber edited comment on PROTON-1898 at 9/11/18 9:51 AM:
---------------------------------------------------------------------
Meanwhile I was running the application also under linux (ubuntu 18.04),
unfortunately with the same result. The memory leak can be seen when sending
and when using AtLeastOnce.
Also I tried use a limited number of message instances only. Each worker (a
single go routine) in my (daemon-like) application used only one message
instance to send and was waiting until the message was settled by receiver.
Then it was sending the next message. I was running 10-50 workers in parallel.
This means there were never more than 10-50 message instances in use. However,
this did not solve the issue. Hence, the leak must be related to delivery
handling (or chunks on socket level?).
Could be the same as discussed in QPID-8134 ...
was (Author: scheiber):
I just wanted to ask for the current state... And, is there any workaround?
> Memory leak related to sending
> ------------------------------
>
> Key: PROTON-1898
> URL: https://issues.apache.org/jira/browse/PROTON-1898
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
> Affects Versions: proton-c-0.24.0
> Reporter: Christoph Scheiber
> Assignee: Alan Conway
> Priority: Major
>
> I started implementing a GO application using qpid electron. There is one
> connection used to receive messages (at-least-once). It works nicely with low
> memory consumption, multiple links and multiple go routines, 50 bytes
> payload, up to 3000 msg/s
> But as soon as the application starts sending messages (to reply over the
> same connection) memory consumption is continuously growing up to 2GB where I
> stopped.
> Even if electron does not leave many options for wrong usage there might be
> an issue in the application.
> So I tried the qpid electron example
> "https://github.com/apache/qpid-proton/blob/master/go/examples/electron/send.go";,
> the same issue.
> To reproduce it:
> * use the sample program, I just added connection options for SASL PLAIN
> * let it send 100000 messages or more to one destination
> My setup:
> * windows 10 pro
> * go1.10.2 windows/amd64
> * qpid 0.24.0-rc1
> * go files and lib build from same git repository clone and branch
> * visual studio 2015, release build, no errors
> * Broker: Solace VMR 8.11.0.1029 with different durable queues as source and
> target
> I tried also qpid proton 0.23.0 earlier, but saw the same problem.
> I tried SendAsync and SendSync, both in 10-50 go routines in
> parallel.Finally, with SendForget my worker routines were soon blocked and
> did not come back.
> Best regards
> Christoph
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
