[Boost-users] [Interprocess] assertion while destroying inexistent named instance

Hi, During my tests I found that if I change the managed shared memory index from the default iset_index to map_index the test fails when a process tries to destroy an already inexistent named instance, using its name. With map_index, an assertion fails when the object is found not to be present. Shouldn't it behave like in the case of iset_index ? Thank you. Rui