[PROTON-1898] Memory leak related to sending

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: proton-c-0.24.0
• Component/s: go-binding
• Assignee: Unassigned
• Reporter: Christoph Scheiber
• Created: 19/Jul/18 18:02
• Updated: 29/Aug/21 10:03

Description

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

 

Issue Links

• relates to: PROTON-1907 [electron/go] Memory leak seen when AtLeastOnce is used