id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
12549	duplicate object created instead of throwing pointer_conflict	Michał Brzozowski <miki@…>	Robert Ramey	"Consider two classes, Father and Child, with a circular dependency. Father contains a Child member, and Child contains a pointer to Father.

There is a way to serialize and deserialize this structure in such a way that an extra object of type Child is created. I believe that pointer_conflict should be thrown during serialization instead.

The created XML archive (see attachment) is consistent, so the extra object is created during deserialization.

I observed this behavior in 1.57 and 1.62."	Bugs	closed	To Be Determined	serialization	Boost 1.62.0	Problem	wontfix