Well, until other people can replicate the problem, it's your unique problem. Congratulations!
Seeing as how the issue occurs when there are an excessive number of talents, and an excessive number of talents only occur with addons... it's not really the problem of the base game.
T-Engine is using an interpreted language, and calling a number of powerful graphics libaries (OpenGL, SDL). It's going to use a good chunk of memory even in normal use.
Solutions (for you, to be done by you):
1) Stop using those addons
2) Re-write the addons yourself
3) Reproduce the problem in the base game (no addons) in such a way that it is reproduceable by at least three other people, at which point it will be a bug that can be addressed
Is this mem use normal?
Moderator: Moderator
Re: Is this mem use normal?
Please help with the ToME wiki!
-
Pile_O_Gunz
- Low Yeek
- Posts: 8
- Joined: Mon Feb 02, 2015 1:16 am
Re: Is this mem use normal?
I'm a developer here's some debugging advise:
Don't worry about the connection attempts it's unlikely they are causing the problem.
It's pretty standard to put the connection attempts into a loop. This loop will likely be on a separate thread of execution from the main game and shouldn't leak memory if coded properly. Even if it did leak there's no reason a chat should be allocating large amounts of memory so a leak here youd expect to see small memory increase over a long period of time.
The problem you are suffering from is called a memory leak. That is when memory is used without being released. Judging by the severity of your problem this is not some small variable not being released but something more substantial like a piece of artwork or a file loaded and not disposed of.
I notice your talking about chat logs and skills list. Don't muddy the waters- focus on 1 bug at a time.
Start with no mods installed can you reproduce ? Yes -nothing to do with the mod, no the mod is a factor.
When debugging software you need to isolate the set of conditions that lead to the reproduction of the bug. Once you done that it will give you a clue where to look in the code.
Find the area of code that handles said situation and look at how it's handling the memory. In c++ memory is allocated on the heap using the new keyword and dealocated using delete. If you don't delete the memory you new you get a leak which is an easy mistake. This leak sounds substantial so it's likely linked to the repeated loading of a resource such as a file or an image. Classes usually have resource cleanup code in the classes deconstructor so that's another place to look.
Don't worry if you don't have the background to find and fix the bug yourself. Just isolating the conditions will be a big help to the Dev.
Don't worry about the connection attempts it's unlikely they are causing the problem.
It's pretty standard to put the connection attempts into a loop. This loop will likely be on a separate thread of execution from the main game and shouldn't leak memory if coded properly. Even if it did leak there's no reason a chat should be allocating large amounts of memory so a leak here youd expect to see small memory increase over a long period of time.
The problem you are suffering from is called a memory leak. That is when memory is used without being released. Judging by the severity of your problem this is not some small variable not being released but something more substantial like a piece of artwork or a file loaded and not disposed of.
I notice your talking about chat logs and skills list. Don't muddy the waters- focus on 1 bug at a time.
Start with no mods installed can you reproduce ? Yes -nothing to do with the mod, no the mod is a factor.
When debugging software you need to isolate the set of conditions that lead to the reproduction of the bug. Once you done that it will give you a clue where to look in the code.
Find the area of code that handles said situation and look at how it's handling the memory. In c++ memory is allocated on the heap using the new keyword and dealocated using delete. If you don't delete the memory you new you get a leak which is an easy mistake. This leak sounds substantial so it's likely linked to the repeated loading of a resource such as a file or an image. Classes usually have resource cleanup code in the classes deconstructor so that's another place to look.
Don't worry if you don't have the background to find and fix the bug yourself. Just isolating the conditions will be a big help to the Dev.