HotRod40
asked on
Memory
Hi,
Can anyone tell me how to create a program as memory efficient as possible.
Do you need to create all objects in code to do this?
Are there any more ways than, Free, FreeAndNil etc to release memory once
my program has finished with it.
I have a program that has a timer and every 10 seconds it runs code to process instructions on a database. I use query's to access the data and also to update my data. But as my program runs, which is 24/7, I can see the Mem Usage in Task Manager slowly accumulating over time. I create all my query's in code and free them up once im finished so I am struggling to think why this memory is accumulating over time.
I am using Delphi 5 Pro and my app is a standard windows exe.
Any help would be greatly appreciated
Thanks
Can anyone tell me how to create a program as memory efficient as possible.
Do you need to create all objects in code to do this?
Are there any more ways than, Free, FreeAndNil etc to release memory once
my program has finished with it.
I have a program that has a timer and every 10 seconds it runs code to process instructions on a database. I use query's to access the data and also to update my data. But as my program runs, which is 24/7, I can see the Mem Usage in Task Manager slowly accumulating over time. I create all my query's in code and free them up once im finished so I am struggling to think why this memory is accumulating over time.
I am using Delphi 5 Pro and my app is a standard windows exe.
Any help would be greatly appreciated
Thanks
Is it possible for this routine to take longer than 10 seconds to complete? If so, depending on how your code was written, you may be creating objects that are already created and then loosing the reference to them.
Just a thought.
You may also have a memory leak somewhere in your code that you may not see right now.
Just a thought.
You may also have a memory leak somewhere in your code that you may not see right now.
if you create objects with AOwner set to self you will not have a memory leak if you close
the application but during the runtime of the programm you will
experience incrementing memory usage
the application but during the runtime of the programm you will
experience incrementing memory usage
ASKER
Gandalf,
Is there any other options to set AOwner to other than Self ?
Thanks
Is there any other options to set AOwner to other than Self ?
Thanks
I've seen code where a form is created with Application as the owner. I personally do not like this coding style. I also don't like to code objects that stick around for longer than they need to be.
However, I have seen some recent posts on EE where they talk about memory leaks in the Query objects (I'm not a DB guy so I'm not really sure if this applies to you). Your code may be correct and the problem may lie elsewhere.
Here are some links
https://www.experts-exchange.com/questions/20815252/Delphi-Memmory-problems.html
https://www.experts-exchange.com/questions/20812633/Careful-Memory-Management.html
Regards,
Rob
However, I have seen some recent posts on EE where they talk about memory leaks in the Query objects (I'm not a DB guy so I'm not really sure if this applies to you). Your code may be correct and the problem may lie elsewhere.
Here are some links
https://www.experts-exchange.com/questions/20815252/Delphi-Memmory-problems.html
https://www.experts-exchange.com/questions/20812633/Careful-Memory-Management.html
Regards,
Rob
you can set the owner to nil
that also means you have to free the objects yourself.
but that also means that you can free the objects at the time you
want and you must not wait until the Owner is freed.
for instance:
procedure formcreate()
begin
myPanel := TPanel.create(nil)
mypanel.parent := Mainform; { to show it somewhere }
...
end;
procedure Formdestroy();
begin
myPanel.free;
...
end;
you can call the mypanel.free anywhere you like
but it also means if you forget it you have a memory leak after the programm is closed
that also means you have to free the objects yourself.
but that also means that you can free the objects at the time you
want and you must not wait until the Owner is freed.
for instance:
procedure formcreate()
begin
myPanel := TPanel.create(nil)
mypanel.parent := Mainform; { to show it somewhere }
...
end;
procedure Formdestroy();
begin
myPanel.free;
...
end;
you can call the mypanel.free anywhere you like
but it also means if you forget it you have a memory leak after the programm is closed
gandalf_the_white is correct, however to avoid any confusion, you can still create the panel with an owner and free it anytime you like before the owner is freed. When this happens, the owner will Remove that component from its internal list so that it knows not to free it when it is destroyed.
However, I still bet the leak isn't in your code but in the components you are using (then again, I haven't seen your code).
Regards,
Rob
However, I still bet the leak isn't in your code but in the components you are using (then again, I haven't seen your code).
Regards,
Rob
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you could:
use less Database object as posssibly
create object dynacmic instead of placing on form
free up (obh.free) after use.
hope helps