Comment 4 for bug 1279534

>> Can you confirm that the behavior is related to how transforms are stored?

yes, same behaviour here, the unexpected behaviour occurs only if I use the option "Preserved Transforms"