when a client connects to the patch server and sends FileInfoReply (client telling the server it's info about the patch file(s) sent by the patch server), the patch server is collecting this list and not emptying it.
eventually Something Bad will happen to the patch server since the PatchServerState.patch_file_info vec is increasing infinitely, and maybe logins will become increasingly delayed since the patch server is validating more and more files as each client connects.
when a client connects to the patch server and sends `FileInfoReply` (client telling the server it's info about the patch file(s) sent by the patch server), the patch server is collecting this list and not emptying it.
http://git.sharnoth.com/jake/elseware/src/branch/master/src/patch/patch.rs#L186
eventually Something Bad will happen to the patch server since the `PatchServerState.patch_file_info` vec is increasing infinitely, and maybe logins will become increasingly delayed since the patch server is validating more and more files as each client connects.
when a client connects to the patch server and sends
FileInfoReply
(client telling the server it's info about the patch file(s) sent by the patch server), the patch server is collecting this list and not emptying it.http://git.sharnoth.com/jake/elseware/src/branch/master/src/patch/patch.rs#L186
eventually Something Bad will happen to the patch server since the
PatchServerState.patch_file_info
vec is increasing infinitely, and maybe logins will become increasingly delayed since the patch server is validating more and more files as each client connects.HAHA OOPS