TFS 0.X MC Problem - One char lagged and another normal

[potinho]

This happened a few times, I have two characters in MC, one has normal ping and the other, apparently for no reason, starts to have high ping. What can cause this? Looking at WinMTR (ping + traceroute) everything seems to be ok.





I dont know if is related, but those are my iptables rules related to OTs:

19   REJECT     tcp  --  anywhere             anywhere             tcp dpts:7171:7172 flags:FIN,SYN,RST,ACK/SYN #conn src/32 > 10 reject-with tcp-reset
20   REJECT     tcp  --  anywhere             anywhere             tcp dpts:7171:7172 state NEW limit: above 40/min burst 40 mode srcip reject-with tcp-reset
22   REJECT     tcp  --  anywhere             anywhere             tcp dpts:7171:7172 limit: above 1499/sec burst 1500 mode srcip reject-with tcp-reset
23   REJECT     tcp  --  anywhere             anywhere             tcp dpts:7171:7172 state NEW limit: above 4/sec burst 5 mode srcip reject-with tcp-reset
24   REJECT     tcp  --  anywhere             anywhere             tcp dpts:7171:7172 limit: above 300kb/s mode srcip reject-with tcp-reset

 

[potinho]

I removed all iptables rule and the problem still happening.

 

[potinho]

Problem still happens...if anyone knows how to fix, i'm paying for solution.

 

[blusterdevtfs]

You mean , if you open two client that will lagged the another one ?

 

[potinho]

You mean , if you open two client that will lagged the another one ?

It's not always, it's rare, but it's annoying and causes problems. Randomly (sometimes once a day, sometimes days go by without happening), one of my characters (I have 4 characters online hunting with bot) simply starts lagging, freezes, gets disconnected from OTCv8, and logs back in immediately with normal ping.

 

[blusterdevtfs]

It's not always, it's rare, but it's annoying and causes problems. Randomly (sometimes once a day, sometimes days go by without happening), one of my characters (I have 4 characters online hunting with bot) simply starts lagging, freezes, gets disconnected from OTCv8, and logs back in immediately with normal ping.

If u had error in ur TFS/OTX post it and also post log ur OTClientv8

 

[potinho]

If u had error in ur TFS/OTX post it and also post log ur OTClientv8

There's no error or warning, both client and server side, like a simple network problem

 

[zyzz7omg]

@potinho I had this same problem, and one thing that helped me a lot was opening debug mode in Client.
At the end, I saw that the freaking quest tracker/questlog module was leaking memory, so I applied the patch:

QuestLog memory leak fix · OTAcademy/otclientv8@491c12b

OTAcademy's fork of OTClientV8. Contribute to OTAcademy/otclientv8 development by creating an account on GitHub.

github.com

Maybe that's the issue you are facing as well, good luck!

 

[potinho]

@potinho I had this same problem, and one thing that helped me a lot was opening debug mode in Client.
At the end, I saw that the freaking quest tracker/questlog module was leaking memory, so I applied the patch:

QuestLog memory leak fix · OTAcademy/otclientv8@491c12b

OTAcademy's fork of OTClientV8. Contribute to OTAcademy/otclientv8 development by creating an account on GitHub.

github.com

Maybe that's the issue you are facing as well, good luck!

I will try, thanks for now

 

[potinho]

@potinho I had this same problem, and one thing that helped me a lot was opening debug mode in Client.
At the end, I saw that the freaking quest tracker/questlog module was leaking memory, so I applied the patch:

QuestLog memory leak fix · OTAcademy/otclientv8@491c12b

OTAcademy's fork of OTClientV8. Contribute to OTAcademy/otclientv8 development by creating an account on GitHub.

github.com

Maybe that's the issue you are facing as well, good luck!

I wasn't using the quest log module (7.72 protocol), but I applied the fix and haven't had any problems for the second day in a row, which might be a good sign.

 

[zyzz7omg]

I wasn't using the quest log module (7.72 protocol), but I applied the fix and haven't had any problems for the second day in a row, which might be a good sign.

Yeah probably it doesn't matter if you actively use it or not, if it has this memory leak bug, eventually gets chunky. If that solved your problem maybe mark the previous message as "solution"? Cheers!

 

[potinho]

@potinho I had this same problem, and one thing that helped me a lot was opening debug mode in Client.
At the end, I saw that the freaking quest tracker/questlog module was leaking memory, so I applied the patch:

QuestLog memory leak fix · OTAcademy/otclientv8@491c12b

OTAcademy's fork of OTClientV8. Contribute to OTAcademy/otclientv8 development by creating an account on GitHub.

github.com

Maybe that's the issue you are facing as well, good luck!

For now seems to work, the disconnections i had was DC issue...i will do more tests but thank you a lot for now man