I can repro pretty consistently if I use CPU slowdown. This seems to be caused by the double clicking. Normally at full CPU speed, I was unable to double click fast enough to trigger this.
What seems to be happening here is that the double click caused the open action to be triggered twice, which is pushing the new file twice to the history stack, thus after the click the navigation history looks like this:
["first existing file.md", "new file.md", "new file.md (currently on this one)"]
Then when you navigate back the first time, it seems to do nothing because it’s on the same file:
["first existing file.md", "new file.md (currently on this one)", "new file.md"]
I think this issue relates to quite a few other issues that are due to either insufficient computer spec, or slow hard disk (or even network drive). The main issue here is that we don’t prevent user-actions from triggering twice when the first one hasn’t “finished”.
I will come back to this one a bit later since I’ll have to make a fix that works for all related issues which is a bit large.
In the meantime, as a workaround, please try to click just once, or at least double click a little slower… Hopefully that gives the machine enough time to respond before issuing another command.