win32 exe memory usage issue
-
Hi All, i have one win32 exe and after executing it, in the task manager the memory usage is increasing even there is nothing to process for exe.At the starting its size is 150kb but it is increasing up to 10 mb. so please can anyone tell me the possible reasons and solutions.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
Hi All, i have one win32 exe and after executing it, in the task manager the memory usage is increasing even there is nothing to process for exe.At the starting its size is 150kb but it is increasing up to 10 mb. so please can anyone tell me the possible reasons and solutions.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
you have memory leak. check your program that every new function match a delete function. remember to release every resource you have got.
-
Hi All, i have one win32 exe and after executing it, in the task manager the memory usage is increasing even there is nothing to process for exe.At the starting its size is 150kb but it is increasing up to 10 mb. so please can anyone tell me the possible reasons and solutions.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
You have got tools to detect whether you have a memory leak. Search for BoundsChecker or Rationals Purify plus.
You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_
-
Hi All, i have one win32 exe and after executing it, in the task manager the memory usage is increasing even there is nothing to process for exe.At the starting its size is 150kb but it is increasing up to 10 mb. so please can anyone tell me the possible reasons and solutions.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Does your debugger report memory leaks in the output window after your binary finishes execution (in debug mode)?
It is a crappy thing, but it's life -^ Carlo Pallini
-
you have memory leak. check your program that every new function match a delete function. remember to release every resource you have got.
-
Does your debugger report memory leaks in the output window after your binary finishes execution (in debug mode)?
It is a crappy thing, but it's life -^ Carlo Pallini
actually i used dbgcntrl apis which shows me dumped memory leaks like this:
strcore.cpp(118) : {83} normal block at 0x008C2F50, 156 bytes long.
Data: < Prov> 01 00 00 00 8F 00 00 00 8F 00 00 00 50 72 6F 76
strcore.cpp(118) : {80} normal block at 0x008C10B0, 33 bytes long.
Data: < C:\P> 02 00 00 00 14 00 00 00 14 00 00 00 43 3A 5C 50
strcore.cpp(118) : {77} normal block at 0x008C1150, 18 bytes long.
Data: < 5555> 01 00 00 00 05 00 00 00 05 00 00 00 35 35 35 35
strcore.cpp(118) : {74} normal block at 0x008C1190, 26 bytes long.
Data: < 192.> 01 00 00 00 0D 00 00 00 0D 00 00 00 31 39 32 2E
{62} normal block at 0x008C14B0, 33 bytes long.
Data: < C > 00 43 00 CD CD CD CD CD CD CD CD CD CD CD CD CD
{61} normal block at 0x008C1500, 40 bytes long.
Data: < |L > 14 7C 4C 10 16 00 00 00 00 00 00 00 00 00 00 00
{59} client block at 0x008C1610, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1610, 64 bytes long
{54} client block at 0x008C1790, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1790, 64 bytes long
{52} client block at 0x008C18B0, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C18B0, 64 bytes long
Object dump complete.but i dont have strcore.cpp file in my workspace and i dont understand the meaning of other errors....
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
actually i used dbgcntrl apis which shows me dumped memory leaks like this:
strcore.cpp(118) : {83} normal block at 0x008C2F50, 156 bytes long.
Data: < Prov> 01 00 00 00 8F 00 00 00 8F 00 00 00 50 72 6F 76
strcore.cpp(118) : {80} normal block at 0x008C10B0, 33 bytes long.
Data: < C:\P> 02 00 00 00 14 00 00 00 14 00 00 00 43 3A 5C 50
strcore.cpp(118) : {77} normal block at 0x008C1150, 18 bytes long.
Data: < 5555> 01 00 00 00 05 00 00 00 05 00 00 00 35 35 35 35
strcore.cpp(118) : {74} normal block at 0x008C1190, 26 bytes long.
Data: < 192.> 01 00 00 00 0D 00 00 00 0D 00 00 00 31 39 32 2E
{62} normal block at 0x008C14B0, 33 bytes long.
Data: < C > 00 43 00 CD CD CD CD CD CD CD CD CD CD CD CD CD
{61} normal block at 0x008C1500, 40 bytes long.
Data: < |L > 14 7C 4C 10 16 00 00 00 00 00 00 00 00 00 00 00
{59} client block at 0x008C1610, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1610, 64 bytes long
{54} client block at 0x008C1790, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1790, 64 bytes long
{52} client block at 0x008C18B0, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C18B0, 64 bytes long
Object dump complete.but i dont have strcore.cpp file in my workspace and i dont understand the meaning of other errors....
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Hi, these add up to a few KB at most, and won't explain what you are seeing. So there probably is no memory leak. Are you allocating some large data structures, say an array of several MB, even when there isn't any reason to already allocate such? :)
Luc Pattyn [Forum Guidelines] [My Articles]
Avoiding unwanted divs (as in "articles needing approval") with the help of this FireFox add-in
-
Hi, these add up to a few KB at most, and won't explain what you are seeing. So there probably is no memory leak. Are you allocating some large data structures, say an array of several MB, even when there isn't any reason to already allocate such? :)
Luc Pattyn [Forum Guidelines] [My Articles]
Avoiding unwanted divs (as in "articles needing approval") with the help of this FireFox add-in
Actually i am receiving some data from server which i am taking in a char * array and after end of story i am deleting it.....and there is nothing big array i am processing with axcept above one....
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
actually i used dbgcntrl apis which shows me dumped memory leaks like this:
strcore.cpp(118) : {83} normal block at 0x008C2F50, 156 bytes long.
Data: < Prov> 01 00 00 00 8F 00 00 00 8F 00 00 00 50 72 6F 76
strcore.cpp(118) : {80} normal block at 0x008C10B0, 33 bytes long.
Data: < C:\P> 02 00 00 00 14 00 00 00 14 00 00 00 43 3A 5C 50
strcore.cpp(118) : {77} normal block at 0x008C1150, 18 bytes long.
Data: < 5555> 01 00 00 00 05 00 00 00 05 00 00 00 35 35 35 35
strcore.cpp(118) : {74} normal block at 0x008C1190, 26 bytes long.
Data: < 192.> 01 00 00 00 0D 00 00 00 0D 00 00 00 31 39 32 2E
{62} normal block at 0x008C14B0, 33 bytes long.
Data: < C > 00 43 00 CD CD CD CD CD CD CD CD CD CD CD CD CD
{61} normal block at 0x008C1500, 40 bytes long.
Data: < |L > 14 7C 4C 10 16 00 00 00 00 00 00 00 00 00 00 00
{59} client block at 0x008C1610, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1610, 64 bytes long
{54} client block at 0x008C1790, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C1790, 64 bytes long
{52} client block at 0x008C18B0, subtype 0, 64 bytes long.
a CDynLinkLibrary object at $008C18B0, 64 bytes long
Object dump complete.but i dont have strcore.cpp file in my workspace and i dont understand the meaning of other errors....
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Ash_VCPP wrote:
{62} normal block at 0x008C14B0, 33 bytes long. Data: < C > 00 43 00 CD CD CD CD CD CD CD CD CD CD CD CD CD {61} normal block at 0x008C1500, 40 bytes long. Data: < |L > 14 7C 4C 10 16 00 00 00 00 00 00 00 00 00 00 00 {59} client block at 0x008C1610, subtype 0, 64 bytes long.
There are probably source files where
newisn't redefined toDEBUG_NEW(probably you added some C/C++ files yourself?). Try to add this definition to all the source files where it isn't present:#ifdef _DEBUG
#define new DEBUG_NEW
#endifThis will enable the debugger to display the exact line numbers in your program where there were memory allocations (that weren't cleaned up).
Ash_VCPP wrote:
but i dont have strcore.cpp file in my workspace and i dont understand the meaning of other errors....
Leaks at strcore.cpp most likely means that you are misusing strings in your program (improper shutdown/termination of a thread that was using strings?). That becomes too much of a big topic to discuss in a reply.
It is a crappy thing, but it's life -^ Carlo Pallini
-
You have got tools to detect whether you have a memory leak. Search for BoundsChecker or Rationals Purify plus.
You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_
Hi Anshuman, i serched for both the tool and i think purifyplus is free downlable but i dont know how to use it so can you please tell me which tool ishould use(depending its a freeware) and where i can get details of using the tool as i didnt got anything on it after googling....:confused:
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
-
Hi All, i have one win32 exe and after executing it, in the task manager the memory usage is increasing even there is nothing to process for exe.At the starting its size is 150kb but it is increasing up to 10 mb. so please can anyone tell me the possible reasons and solutions.
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
If your codes is not very long,put it out. We can find the problem for you. I think that must be a memory leak. I am a Chinese boy.My English is poor...
-
hi, i checked new/delete sequence there is all fine, is there anything else which can cause memory leak or how can i detect memory leak...
Thanks A Ton Ash_VCPP walking over water is just knowing where the stones are.....
Visual Leak Detector[^] is a good friend.