search

Google-Code-Fork / tibiaapi

Automatically exported from code.google.com/p/tibiaapi
MIT License
0 stars 0 forks source link

Memory Leak? #209

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.sending packets.. ie client.console.say()
2.
3.

What is the expected output? What do you see instead?
every time the packet gets send it increases the size of tibia.exe in memory...

What version of the product are you using? On what operating system?
2.9.40 for 8.57

Please provide any additional information below.

Original issue reported on code.google.com by bartlomi...@gmail.com on 3 Jul 2010 at 6:28

Attachments:

GoogleCodeExporter commented 9 years ago 
*sent* :P

Original comment by bartlomi...@gmail.com on 3 Jul 2010 at 6:33

GoogleCodeExporter commented 9 years ago 
I'm gonna assume I know the answer to this, but I'm going to ask anyways. Are 
you sending the packet via proxy, hook, or memory?

Original comment by joebingham07@gmail.com on 5 Jul 2010 at 3:04

GoogleCodeExporter commented 9 years ago 
I guess memory, since I did not get proxy or hook proxy to work yet ;d
How do I fix this? After running a bot for few hours the tibia consumes over 
120Mb of memory and it crashes

Original comment by bartlomi...@gmail.com on 13 Jul 2010 at 4:24

GoogleCodeExporter commented 9 years ago 
The memory method it's just for a small things, if you are making a more 
complex bot you should use the proxy or the hook proxy.

Original comment by brunodun...@gmail.com on 26 Jul 2010 at 2:41

GoogleCodeExporter commented 9 years ago 
As bruno stated, the memory method is more like a proof-of-concept feature than 
something that should be used for heavy packet use. You should look in to using 
either the proxy or hook proxy (packet hook) for your needs.

Original comment by joebingham07@gmail.com on 29 Sep 2010 at 4:43