Using non scalar element type for the buffer leads to crash

[Alex-PLACET]

Using non scalar element type like std::string, leads to a crash in the deallocation code.

[JohanMabille]

After some investigations, it crashes if the initial string buffer is allocated with operator new[] instead of using the standard allocator:

{
    std::size_t size = 8u;
    std::string* raw_buf = new std::string[size];
    buffer<std::string> buf(raw_buf, size);
    // Wil crash when getting out of scope
}

Replacing the allocation with buffer<std::string>::allocator_type alloc; alloc.allocate(size); fixes the issue.

[JohanMabille]

Under Linux with gcc, the reason is that internally, std::allocator<T>::allocate calls _GLIBCXX_OPERATOR_NEW , which might be different from operator new