安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
Since it's not reproducible, I guess it will remain a mystery ...
Edit: I was speaking to one of my old testers about it and according to them, this bug occurred when the log folder overflowed. Can any of you confirm if your log folders were overflowing when the bug occurred?
An observation about large amounts of logs being the problem though: isn't every server in T crashing rediculously often and thus generating so many logs (I legit sat there for a minute when I did a rm * in one of the last T nodes). Is it possible for you to disable the logs that are generated on crash in your extension? I feel like that might at least reduce this problem if it is based on having too many logs.
♥♥♥♥
Guess you just have to clean out the log folder every couple of hacks.