Remote cross-platform MFC has risk of gem crash
Running a markForCollection (MFC) from a remote gem that is on a machine
with a different byte order than the stone, and therefore requires swizzle,
can result in a gem crash with a preceeding message in the log:
"ObjSupSwizzlePageGet error on page 16778280 oop 10944580 (message can
be ignored if no further problems)"
Byte swizzling is required when a remote gem is Windows or Linux, and the
stone on Solaris, AIX or HP (or vice versa).
Avoid running MFC from gems that are remote from the stone and on a machine
with a different byte ordering.