Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
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.