[PROTON-611] [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.7
• Fix Version/s: proton-0.8
• Component/s: proton-c
• Assignee: Andrew Stitcher
• Reporter: Dominic Evans
• Created: 19/Jun/14 08:43
• Updated: 10/Oct/14 12:37
• Resolved: 11/Aug/14 22:17

Description

transport_produce attempts to allocate a negatively sized buffer

As soon as remote_max_frame is set, the code in transport_produce attempts to increase its buffer immediately up to that size when its initial size isn't enough. This causes a huge malloc to occur if the remote max frame size is large and also potentially overflows MAX_INT