[ 
https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093428#comment-14093428
 ] 

ASF subversion and git services commented on PROTON-611:
--------------------------------------------------------

Commit 1617376 from [~astitcher] in branch 'proton/trunk'
[ https://svn.apache.org/r1617376 ]

PROTON-611: Don't allocate frame_max bytes immediately, grow by factors of 2 
until
you get to the max - else a large frame size can blow away 4Gb of memory!

> [proton-c] transport buffer increased to peer's max frame size if initial 
> output_size is not enough
> ---------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-611
>                 URL: https://issues.apache.org/jira/browse/PROTON-611
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>            Reporter: Dominic Evans
>            Assignee: Andrew Stitcher
>         Attachments: 20_fix_bad_malloc_in_transport_produce.patch
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to