Re: [boost] [serialization] [1.35.0] Potential Memory Buster, Deserializing std::vector<T, boost::pool_allocator<T> >

From: Matthias Troyer (troyer_at_[hidden])
Date: 2008-06-14 05:27:26

On Jun 13, 2008, at 9:55 AM, Dean Michael Berris wrote:

> Hi Everyone,
>
> In the 1.35.0 release, I see that boost/archive/array/iarchive.hpp has
> a commented out 'load_optimized' function which is not commented out
> in the trunk.
>
> When deserializing to an std::vector<uint32_t,
> boost::pool_allocator<uint32_t> >, I see that the optimized
> implementation will first get the correct size, set the receiving
> container's size correctly, and then put the contents of the array
> into the container.
>
> The question I have is why is this function commented out in the  
> 1.35.0 release?

We commented this out since we found out just before the release that  
this optimization prevents tracking of vectors. 1.36 will implement  
this in a slightly different way, which will enable some more  
optimizations.

Matthias