We've tracked this down to a bug in Native X10's serialization code. The
bug was introduced in X10 2.2.2.
It will show up as memory corruption when transmitting multiple objects
that implement x10.io.CustomSerialization across an at boundary. The most
likely way for this to surface in user code is if you send multiple
instances of collection classes like HashMap or ArrayList that implement
CustomSerialization between places in a single at statement.
We'll pull this fix into a 2.2.2.1 release within the next week.
Thanks to Christopher for reporting the bug and making his code available
to help us track it down!
--dave
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
