Board somehow skips to end while reviewing

Recently I’ve noticed while analyzing my games with AI after playing that somehow it keeps skipping to the end of the game. I can’t figure out why this happens. As best I can tell it occurs randomly. I don’t think I’m fat fingering anything, but is there some key combo or mouse gesture that does this? Has anyone else seen this? This is happening several times a review now and is really frustrating. Especially since reviewing with AI is OGS’s killer feature.

2 Likes

Some additional information, I’m now quite certain that the keyboard is not involved. It seems to happen mainly when I’m looking at variations, but that could be a red herring. It’s happened four times so far for the review I’m in the middle of… :grimacing:

2 Likes

Acknowledged, it’s on the to-fix list :slight_smile:

2 Likes

Thanks!

1 Like

@anoek, in case it’s helpful, here’s a stack trace that seems to be from when the error occurs:

computAverageMoveTime passed undefined instead of a time_control object
t.computeAverageMoveTime @ GoUtil.ts:222
t.isLiveGame @ util.ts:500
(anonymous) @ Game.tsx:579
l.emit @ index.js:181
e.emit @ TypedEventEmitter.ts:50
(anonymous) @ GobanCore.ts:813
n.emit @ index.js:133
n.onevent @ socket.js:270
n.onpacket @ socket.js:228
(anonymous) @ index.js:21
n.emit @ index.js:133
n.ondecoded @ manager.js:345
(anonymous) @ index.js:21
n.emit @ index.js:133
s.add @ index.js:241
n.ondata @ manager.js:335
(anonymous) @ index.js:21
n.emit @ index.js:133
n.onPacket @ socket.js:457
(anonymous) @ socket.js:274
n.emit @ index.js:133
n.onPacket @ transport.js:145
n.onData @ transport.js:137
ws.onmessage @ websocket.js:147
1 Like