Closed piotrrak closed 1 year ago
I think this might be a libc++ bug look at the stack it’s from range_error that calls free directly, where runtime_error called operator new.
The call stack suggests it’s not the allocator but the destruction of the memory allocated by the std::runtime_error (probably for storing the error string)
Closing due to being libc++ issue
Hello again,
So, it seems we're allocating memory for an exception as
throwing<void, void>
but trying to free it asthrowing<void, std::allocator<?>>
?I see we will be using
std::allocator_traits<void>
anyhow for promise allocation and how the exception is allocated by operator new, but don't see howexception_object_delete<void>
does anything else than delete here.Please see log below: