- Do you happen to have a backtrace ? - Does it fail when you create a subscription or when you try to deserialize a message? - Do you have the same problem with message types that are of known size (like uint64t) ? Can you reproduce it with a pure C communication ? (running [test_messages_c](https://github.com/ros2/system_tests/blob/master/test_communication/test/test_messages_c.cpp) from test_communication for example) I would expect the problem to be the same but that would at least allow you to rule out anything Python related. My guess is that it may be something in the coreDX C typesupport. We test only Fast-RTPS on aarch64 ATM that uses the introspection mechanism. It's possible that the alignment (and thus the pointers you access and free) are not correct when its built for aarch64. [quote="BrannonKing, post:1, topic:3057"] PS, FastRTPS still spews a lot of this when I run the listener: [RTPS_HISTORY Error] Change payload size of 8808 bytes is larger than the history payload size of 5000 bytes and cannot be resized. -> Function add_change [/quote] Can you please provide more details on the related thread (https://discourse.ros.org/t/payload-size-error-with-fastrtps/2815) --- [Visit Topic](https://discourse.ros.org/t/error-using-python3-nodes-on-arm64-coredx/3057/2) or reply to this email to respond. If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates. ______________________________________________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users Unsubscribe: