RPTools.net

I haven't found any example on how to force timsort to throw that exception in a comparable situation. It is generally a bad idea to have comparators not being consistent with equals and the zorder-comparator isn't, because tokens with the same GUID can have different z-order. I have tried a bit to force the exception but couldn't. It probably requires corrupt tokens to have the same GUID (as already suggested). It would be a good idea to have equality checked first in this comparator.

I'd say the OP was satisfied with his huge map being saved and not interested in the root cause, chances are slim that we get an example file *and* drag-drop to work as on his machine.