 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
 Posted: Fri Oct 12, 2007 7:13 pm
[2.05] GDI leak
|
A continuing increase in the memory usage and a really ugly display is shown using this procedure
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#WINDOW test;#CLOSE test" at the command line without the quotes
4. Repeat 3 until you are tired of having memory eaten.
Note the memory usage at this point
5. Close the left over test items
Memory usage unchanged here
6. Do step 3 again until satisfied
Memory usage continues to climb
My quick investigation of it at later points made it seem that 6 brushes were being created each time and never released. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
Posted: Fri Oct 12, 2007 7:28 pm
|
The same leak is noticeable without the #CLOSE in there, it saves on the eye sore display.
1. Launch CMud
2. Close Sessions Window (ESC)
3. Enter "#WINDOW test" at the command line without the quotes
4. Close test window by clicking X
5. Repeat 3 and 4 as needed to find leak
It still looks like 6 brushes, and a small amount of memory each time. The memoryis likely where the handles for those brushes are being stored. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Oct 12, 2007 10:15 pm
|
Hmm, not sure. My memory leak detector isn't catching these. I'll have to do a more serious GDI analysis. It's also possible that they are "known" leaks in Delphi that I cannot fix (the FastMM memory leak detector doesn't report known Delphi leaks).
Since this isn't something that will cause a problem in normal usage, I'm not going to worry about it until I get to the optimization stage closer to public release. |
|
|
|
|
|
|
|
