qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough
Date Thu, 19 Jun 2014 16:36:25 GMT

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

Andrew Stitcher commented on PROTON-611:
----------------------------------------

Dominic,

* Can we confirm that this is a problem in the released 0.7 rather than the trunk 0.8 code?
* Do you have a specific test case that exhibits this bug?

Thanks

> [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)

Mime
View raw message