MRU order gets randomly corrupted

[gliviu]

Atom 1.7.2 installed without any extension.
Pretty difficult to reproduce due to random nature. However here is what I've done:

• open 3 tabs
• switch tabs multiple times
• after 20-30 switches the mru order should be broken

[amytruong]

I haven't been able to reproduce this but will keep an eye out since you did say it happens randomly. When you say the MRU order is broken, do you mean the tabs are out of the MRU order? Or does something else happen?

[gliviu]

Tabs are out of mru order.

[gliviu]

Here is a quick example.

Initially the order is 321. I ctrl+tab once and the order becomes 231. I ctrl+tab again and I expect to switch to tab 3. But it switches to 1.

[ngoue]

[Corrupted MRU Bug Report]

Repro Steps

1. Open two new tabs
2. Switch tabs using pane:show-item-1 or pane:switch-item-2 (this should work)
3. Reorder tabs using pane:move-item-left or pane:move-item-right
4. Try switching tabs again with pane:show-item-1 or pane:show-item-2
   NOTE Commands can be run either with keyboard shortcuts or from the command palette with the same result

Expected: Adjust order of tabs
Actual: MRU order gets corrupted

Command History

     -0:11.7 pane:show-item-1 (atom-text-editor.editor)
     -0:11.4 pane:show-item-2 (atom-text-editor.editor.is-focused)
     -0:10.3 pane:move-item-right (atom-text-editor.editor)
     -0:10.0 pane:move-item-left (atom-text-editor.editor)
     -0:09.1 pane:show-item-1 (atom-text-editor.editor)
     -0:08.7 pane:show-item-2 (atom-text-editor.editor)
     -0:08.4 pane:show-item-1 (atom-text-editor.editor.is-focused)
     -0:08.1 pane:show-item-2 (atom-text-editor.editor)

Versions

• Atom: 1.7.3
• Atom-Shell:
• OS: Mac OS X 10.11.5
• Misc
  • apm 1.9.2
  • npm 2.13.3
  • node 0.10.40
  • python 3.4.2
  • git 2.2.1

---

This report was created in and posted from the Atom editor using the package bug-report v0.7.1.

[ngoue]

It only takes me 1-2 moves left or right to reproduce.

[wprater]

this happens quite often for myself as well.

[Ben3eeE]

This sounds like the issue that was fixed in #302. If you can reproduce this in Atom 1.11 or later please comment here and we will reopen.

[iolsen]

I've discovered that the key-up key binding responsible for resetting the MRU stack isn't reliably being caught. I expect that's the primary cause of this issue. There will be a fix soon, likely this week, and I'll reference this issue and reclose at that time.