[
https://issues.apache.org/jira/browse/THRIFT-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112844#comment-18112844
]
Sylwester Lachiewicz edited comment on THRIFT-5149 at 9/8/26 2:13 PM:
----------------------------------------------------------------------
-Container size limits exist in the C++ runtime: {{maxContainerSize}}
enforcement in
[lib/cpp/src/thrift/protocol/TBinaryProtocol.h|https://github.com/apache/thrift/blob/master/lib/cpp/src/thrift/protocol/TBinaryProtocol.h].
Resolving as Fixed.-
was (Author: slachiewicz):
Container size limits exist in the C++ runtime: {{maxContainerSize}}
enforcement in
[lib/cpp/src/thrift/protocol/TBinaryProtocol.h|https://github.com/apache/thrift/blob/master/lib/cpp/src/thrift/protocol/TBinaryProtocol.h].
Resolving as Fixed.
> Limit container byte size
> -------------------------
>
> Key: THRIFT-5149
> URL: https://issues.apache.org/jira/browse/THRIFT-5149
> Project: Thrift
> Issue Type: Wish
> Components: C++ - Library
> Reporter: Antoine Pitrou
> Priority: Major
>
> The C++ library currently takes a container size limit which can avoid
> instantiating too large containers, limiting the possibility of memory bombs.
> However, some container elements may be very large and preallocating such a
> large container may blow up memory even if the number of elements "looks"
> reasonable. This allows for very small files to blow up memory (and therefore
> to be potential denial-of-service material).
> It would be nice to have an additional parameter to limit in-memory container
> byte size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
