2 Oct
2008
2 Oct
'08
6:02 p.m.
From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Phil Bouchard Sent: Thursday, October 02, 2008 12:34 PM
I will verify this but what I personaly get is a ordered_malloc() failure on the 2005th attempt. 3 blocks of memory get allocated / deallocated over and over until the allocation routine fails.
If unchecked, it eventually crashes for me inside of simple_segregated_storage::try_malloc_n(), which I believe is what you're seeing. The stack trace I quoted in my previous e-mail is the trace of the errant write that corrupts the pool. -Chris