I have seen this happen quite often as well. It seems to "ghost" some measures at the end of a song if you are doing heavy editing. My way around it is to save, close and reopen the song file. That clears the editing cache from your temp folder. RB saves at every edit so your CTL+Z undo will work.

I have not tried clearing my temp folder while RB is open. It's just as fast for me to close and reopen. I will try that the next time I go upstairs and work. If it does I will just write a 2 line batch file and run it from the desktop. That will allow me to use Windows+D to get to desktop, run that batch file, then go back to work.

I once saw ghosting like this that was something like 12 bars after the end of the song. RB just randomly pasted some junk there. I agree with the logic that yeah, it isn't a big deal to erase those measures with a cut, but why should we have to? This is obviously a glitch and it needs to be fixed. I only go back as far as maybe 2009 with PG software but I have had this anomaly for 7 years and it should be fixed. My analogy is that when a drain leaks you can put duct tape around it or have the plumber that put the drain in fix it to work like it was supposed to. Those who have read my posts here know my feelings about software bugs. Workarounds and band-aids are not acceptable to me. What is baffling is that if you speak to 100 people, 60 have no issues, and the other 40 have different issues. These things pop up at random and there is on consistent pattern to the bugs. Computers and software are not supposed to work like that. If one user has a bug, everybody should, because there is no PG for just Bob, or for just Fred, or for just Sam... every copy is the same root software with more amenities added for the different versions. (That is from the nerd perspective.) I really dislike companies that let things go because they know there is a way around a problem. (You listening, Micro$oft?) Fix the problem.