[Crash, Zen browser] Index 16 is past the end of a fully-loaded parent

[tekumara]

Crash Details

Browser: Mozilla firefox 145.0.1 20251119061732 (mac aarch64)
Extension: Tab Stash 3.3 (normal)

Index 16 is past the end of a fully-loaded parent
insertNode@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:9764:13
whenTabMoved@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:11814:15
handler@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:9705:16


Index 16 is past the end of a fully-loaded parent
insertNode@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:9764:13
whenTabCreated@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:11755:15
Model8/<@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:11405:36


Index 16 is past the end of a fully-loaded parent
insertNode@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:9764:13
whenTabCreated@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:11755:15
Model8/<@moz-extension://54248611-07f0-482a-a65e-208c03645f25/assets/launch-vue.js:11405:36

Non-Standard Browser Settings

Zen browser

Installed Extensions

n/a

Describe the Crash

1. Open a tab
2. Pin the tab, by moving it to the pinned section
3. Unpin the tab, by moving it out of the pinned section
4. Tab stash crashes

Expected Behavior

No response

Impact

No response

Additional Details

No response

Vote for This Issue

• [x] Readers: If you are also experiencing this problem, please vote for it by giving the ORIGINAL POST a thumbs-up using the :smiley: button below. You are welcome to leave comments and discuss the issue if you have more details to add, but "Me too!" comments are not counted by the voting system.

[josh-berry]

hm, are you able to reproduce this in Firefox at all? I have not been able to, so it seems possible this is a bug in Zen itself reporting tabs at the wrong positions.

[tekumara]

Thanks for the quick response! No unfortunately I can't reproduce on Firefox either. I think Zen is doing something different here from Firefox when pinning tabs.

[josh-berry]

Yep, this is a bug in Zen. I happened to have it installed and played with it a little, and their extension API seems to be leaving gaps in the list of tabs. Notice how the index: field jumps from 3 to 5 here after unpinning a tab:

await browser.tabs.query({})
Array(12) [ {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, … ]
​0: Object { id: 3, index: 0, windowId: 5, … }
​1: Object { id: 4, index: 1, windowId: 5, … }
​2: Object { id: 5, index: 2, windowId: 5, … }
​3: Object { id: 6, index: 3, windowId: 5, … }
​4: Object { id: 11, index: 5, windowId: 5, … }
​5: Object { id: 12, index: 6, windowId: 5, … }
​6: Object { id: 13, index: 7, windowId: 5, … }
​7: Object { id: 1, index: 8, windowId: 5, … }
​8: Object { id: 9, index: 9, windowId: 5, … }
​9: Object { id: 10, index: 10, windowId: 5, … }
​10: Object { id: 14, index: 11, windowId: 5, … }
​11: Object { id: 2, index: 12, windowId: 5, … }
​length: 12
​<prototype>: Array []

Tab Stash expects tabs in the same window to be positioned consecutively according to each tab's index (as this is what the tabs API requires). So you may want to raise this issue with the Zen folks.