Help my memory leaks

[gigglie]

Do increasing stack space in the mmp always increases stacks allowable space in the phone ? I have increased my allowed stack space but my program still leaks memory .
Also is there any good basic memory management program apart from the following ?
1. Declare variables in global scope whereever possible .
2. CleanupStack.
3. User::CompressAllHeaps (Is there any equivalence in stack ?)
4. Take more resources from rss , reduce dynamic declaration
5. Heap variables to replace stack ones .
6. Less datatype inter-conversions .

Also does image heap results in memory leaks ? I have so many images here .

[yogpan]

Hi,
Memory leaks are not because of stack size or heap size it is because of the programmer's mistake of leaving some memory orphan( without deletion).
Now the memory leak can be because of several errors forgetting to delete the object properly or completely, leaving resource handles open.
There are different tools to detect memory leak like HookLogger for emulator also Macros like UHEAP_MARK and UNMARK are also practiced to detect memroy leaks.
Here are some good articles on memory leak in wiki
http://wiki.forum.nokia.com/index.php/Memory_leaks
http://wiki.forum.nokia.com/index.ph...ing_techniques
http://wiki.forum.nokia.com/index.php/Hooklogger

[stenlik]

Hi,

as yogpan said - memory leaks are bugs in your C++ code...

BR
STeN

P.S. I think CompressAllHeaps() is deprectaed on S60 3rd.

[hotcheese]

As already said, you have some very big misunderstanding on what the stack and heap is - in particular asking if you can compress the stack or if increasing it will remove a memory leak.

The stack and the heap are things in all computers, maybe you should take some time to read about them as without knowing what they are you can't understand how they can be misused in symbian.

[vasant21]

Do increasing stack space in the mmp always increases stacks allowable space in the phone ? I have increased my allowed stack space but my program still leaks memory .
Also is there any good basic memory management program apart from the following ?
1. Declare variables in global scope whereever possible .
2. CleanupStack.
3. User::CompressAllHeaps (Is there any equivalence in stack ?)
4. Take more resources from rss , reduce dynamic declaration
5. Heap variables to replace stack ones .
6. Less datatype inter-conversions .

Also does image heap results in memory leaks ? I have so many images here .

1) First and foremost make sure that you use cleanup stack, two phase construction where ever required.

2) Make sure you properly delete all the members in the destructor and free all the resources if any.

3) Go thru your code and try to check for automatic/temporary/local heap objects and check if you properly delete them, also check if you are allocating memory in a loop somewhere.

4) Similarly check for any Handles, Generally 'R' Classes, make sure that you close/release them properly, try using CleanupClosepushL() with them.

These are the things that can be kept in the mind, but of course you have a memory leak already and hooklogger is one tool i use for detecting memory leaks, and it works quite well.