It seems that the problem also exists with only open-tabs-next-to-current enabled and this extension disabled. I suggest reporting it to open-tabs-next-to-current.