CNR. Please provide a test map that shows this behaviour so we can check it out. Also confirm the steps - which layers are selected, which tools you are using, which track to move etc.
>>
If this is reproducable, we'll need the route. As always, if you disable items and work out which item is causing the problem that makes our task much easier.
Based upon the assertions and crashes, I would suspect the route may be corrupt. I would recommend that you ensure all the dependency assets required are enabled (restart if they were disabled) and run a Delete Missing Assets. This will renumber assets on the route and may resolve the issues you're seeing.
UPDATE:
I was able to solve the track moving, but not the track-objects doing so at the same time, by running delete missing assets even though there are none on two routes I discovered the problem with. There were no layers other than the bog standard route and session so that wasn't the issue, although, I did check to make sure.
I will look at the ones that CTD and if they can't be resolved I'll toss them and move on. It's time to do some pruning of my routes and content and as always there will be a backup done first just in case I want to readdress this issue at a later date.
The humongous copy followed by the massive EDR is what prevented me from beta testing now that I know that two TRS19-Plus copies can't run at the same times should I want to join an MPS session.