From 8d2665ebd77eda97a1f8a747bd6d458d9a8c7e48 Mon Sep 17 00:00:00 2001 From: genxium Date: Mon, 19 Dec 2022 14:56:56 +0800 Subject: [PATCH] Updated comments. --- frontend/assets/scripts/WsSessionMgr.js | 1 + 1 file changed, 1 insertion(+) diff --git a/frontend/assets/scripts/WsSessionMgr.js b/frontend/assets/scripts/WsSessionMgr.js index 559f2c7..6d35914 100644 --- a/frontend/assets/scripts/WsSessionMgr.js +++ b/frontend/assets/scripts/WsSessionMgr.js @@ -144,6 +144,7 @@ window.initPersistentSessionClient = function(onopenCb, expectedRoomId) { if (null == evt || null == evt.data) { return; } + // FIXME: In practice, it seems like the thread invoking "onmessage" could be different from "Map.update(dt)", which makes it necessary to guard "recentRenderCache & recentInputCache" for "_generateInputFrameUpsync & rollbackAndChase & onRoomDownsyncFrame & onInputFrameDownsyncBatch" to avoid mysterious RAM contamination, but there's no explicit mutex in JavaScript for browsers. try { const resp = window.pb.protos.WsResp.decode(new Uint8Array(evt.data)); //console.log(`Got non-empty onmessage decoded: resp.act=${resp.act}`);