Game doesn't seem to end

[flugsio]

http://en.lichess.org/7fMTtjqE/black

lichess-rs0:PRIMARY> db.game5.find({"_id": "7fMTtjqE"});
{ "_id" : "7fMTtjqE", "is" : "lS8M8Ufk", "us" : [ "thomasss4567", "fbustillo" ], "p0" : { "e" : 1422 }, "p1" : { "e" : 1717 }, "ps" : BinData(0,"NFADEGZgAGAABiQGAA
AGAAXuAAAOAAwA7Qze7rAKC5A="), "s" : 20, "t" : 23, "c" : BinData(0,"CQYAL+gAB6IAAG4B"), "cl" : BinData(0,"CDAACv8="), "mt" : BinData(0,"lYmZxqa42arV27qg"), "ra" : t
rue, "ca" : ISODate("2016-03-22T17:14:51.923Z"), "ua" : ISODate("2016-03-22T17:19:33.435Z"), "so" : 1, "ck" : ISODate("2016-03-22T18:14:51.923Z"), "pl" : [ "thomas
ss4567", "fbustillo" ], "pg" : BinData(0,"IxR8QB1ToCUrbYBqQBycgJyAYkhmoEyo3oABOg0aTqBqgEDAQMA="), "ph" : BinData(0,"J7LDWce4U29ViAu5")

There seems to be multiple games stuck, checkAt is not updated
db.game5.find({"ck":{$lt: ISODate("2016-03-22T23:40:00.000Z")}});

This should sweep them up I thought, I didn't have more time to investigate if there was some issue with the data
https://github.com/ornicar/lila/blob/master/modules/round/src/main/Titivate.scala#L37

Player can't resign becuase the UI has no buttons for it, and is thereby blocked from the lobby as a result (shouldn't the lobby have a big abort-button though?).

http://en.lichess.org/forum/lichess-feedback/unable-to-play-chess-on-the-site

[flugsio]

It happened again, http://en.lichess.org/VFYuTaNe the timed out player might not have been on the page and titivate is probably broken somehow

23:06:29         flugsio | did you have connection problems?
23:06:42         flugsio | and how did it end, did your time just run out?
23:07:00         parrotz | i think i may have
23:07:13         parrotz | i premoved and waited, then refreshed page like 3 minutes later

Related commits after first report and this instance:
a726ee9#diff-db2b1cf882bfcd3c3af45118ee5c8eee
402e1e2#diff-db2b1cf882bfcd3c3af45118ee5c8eee
249ebbf#diff-db2b1cf882bfcd3c3af45118ee5c8eee
Some older change 363f636#diff-db2b1cf882bfcd3c3af45118ee5c8eee

sudoing the game reveal outoftime spamming, claim draw/victory or manually sending resign doesn't work. http://i.imgur.com/AMFdTOD.png Even if titvate is dead maybe it could be fixed by listening to these outoftime messages?

lichess-rs0:PRIMARY> db.game5.find({"ck":{$lt: ISODate("2016-04-02T21:35:00.000Z")}}, {"_id": 1, "s": 1, "cl": 1, "ca": 1, "ck": 1});
{ "_id" : "muRZJ5A8", "s" : 20, "cl" : BinData(0,"B9YACZk="), "ca" : ISODate("2016-03-31T20:28:15.232Z"), "ck" : ISODate("2016-03-31T21:28:15.232Z") }
{ "_id" : "UTUWvZZe", "s" : 20, "cl" : BinData(0,"+RsAADU="), "ca" : ISODate("2016-04-01T01:02:41.585Z"), "ck" : ISODate("2016-04-01T02:02:41.585Z") }
{ "_id" : "Aj21eReN", "s" : 20, "cl" : BinData(0,"CpsAEi0="), "ca" : ISODate("2016-04-01T03:26:50.166Z"), "ck" : ISODate("2016-04-01T04:26:50.166Z") }
{ "_id" : "2p6M48pU", "s" : 20, "cl" : BinData(0,"ya4ADjE="), "ca" : ISODate("2016-04-02T06:09:36.184Z"), "ck" : ISODate("2016-04-02T07:09:36.184Z") }
{ "_id" : "nTJiYmhv", "s" : 20, "cl" : BinData(0,"BtMABK8="), "ca" : ISODate("2016-04-02T06:13:39.610Z"), "ck" : ISODate("2016-04-02T07:13:39.610Z") }
{ "_id" : "k60lSjwp", "s" : 20, "cl" : BinData(0,"+OQAAK0="), "ca" : ISODate("2016-04-02T19:38:40.044Z"), "ck" : ISODate("2016-04-02T20:38:40.044Z") }
{ "_id" : "YI9hMnHK", "s" : 20, "cl" : BinData(0,"BR4ACVE="), "ca" : ISODate("2016-04-02T20:29:07.037Z"), "ck" : ISODate("2016-04-02T21:29:07.037Z") }
{ "_id" : "qcrCkbhI", "s" : 20, "cl" : BinData(0,"AhkAAuE="), "ca" : ISODate("2016-04-02T20:31:51.764Z"), "ck" : ISODate("2016-04-02T21:31:51.765Z") }
{ "_id" : "VFYuTaNe", "s" : 20, "cl" : BinData(0,"DHgAAj4="), "ca" : ISODate("2016-04-02T20:32:08.106Z"), "ck" : ISODate("2016-04-02T21:32:08.106Z") }
{ "_id" : "PRXNqyGo", "s" : 20, "cl" : BinData(0,"BpMAASk="), "ca" : ISODate("2016-04-02T20:32:35.807Z"), "ck" : ISODate("2016-04-02T21:32:35.807Z") }
{ "_id" : "cBcSO4kl", "s" : 20, "cl" : BinData(0,"+aQAAPY="), "ca" : ISODate("2016-04-02T20:32:40.925Z"), "ck" : ISODate("2016-04-02T21:32:40.925Z") }

[ornicar]

I don't know what's going on. Titivate seems to run normally. The bug disappears when I load the faulty game to my local instance.

[ornicar]

there's no sign of it anymore in the monitoring. For some reason.