Is it possible that this might be related to the recently discovered fact (at least by me) versions of the serialization library are, contrary to intention, not thread safe? That is, conflict occurs when multiple threads are using serilization even with different archive instances due to the fact that they share the same gobal extended_type_info table. This has been addressed - and hopefully remedied in 1.35. Robert Ramey Sergey Filippov wrote:
Sigurd Saue
writes: Thanks. You are probably right - interesting to hear if anyone else has had the same problem.
I will try the other approaches shortly.
Sigurd,
I believe I have the same problem. My code fails to serialize a polymorphic class though the pointer to the base with the "unregistered class" error. The code works well on 32-bit Windows, but fails on 64-bit. However, the failure occurs only on one customer's machine (8 processors), I could not reproduce it on any of my test computers, including 64-bit with 4 processors.
Did you find a workaround? Probably one of mentioned by Robert, or another one? Your help would be greatly appreciated.
Sergey