UI locks up w/ gui.$refs.cntrl is undefined error

[brannondorsey]

Loose steps to reproduce:

1. Load page
2. Filter by Norwegian
3. Click through messages for a while until the UI hangs and the following error gets spit to the console:

debug-menu.js:27:5
TypeError: gui.$refs.cntrl is undefined
Stack trace:
@http://localhost:8000/mftm-frontend/js/main.js:84:9
r.prototype.emit@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:12370
r.prototype.onevent@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:26291
r.prototype.onpacket@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:25910
t.exports/<@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:28031
r.prototype.emit@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:12370
r.prototype.ondecoded@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:18957
t.exports/<@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:28031
r.prototype.emit@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:12370
s.prototype.add@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:10709
r.prototype.ondata@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:18902
t.exports/<@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:28031
r.prototype.emit@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:12370
r.prototype.onPacket@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:28100
r.prototype.setTransport/<@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:25715
r.prototype.emit@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:1:12370
r.prototype.onPacket@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:8003
r.prototype.onData@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:7952
r.prototype.addEventListeners/this.ws.onmessage@http://localhost:8000/mftm-frontend/js/libs/socket.io.js:2:22191

[brannondorsey]

On second thought, I just retried those steps and things worked fine. Not sure how to reproduce yet, but that stack trace should give a hint.

[brannondorsey]

Weird... navigating off the page to comment on this issue, and then returning, triggered the bug.

[nbriz]

...weird