You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Dominic Evans (JIRA)" <ji...@apache.org> on 2014/09/11 14:42:34 UTC
[jira] [Closed] (PROTON-611) [proton-c] transport buffer increased
to peer's max frame size if initial output_size is not enough
[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Evans closed PROTON-611.
--------------------------------
> [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
> Fix For: 0.8
>
> 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.3.4#6332)