can we efficiently find the memory leaks through task manager?
is it a good way?
thanks a lot
RaviKishore.
Printable View
can we efficiently find the memory leaks through task manager?
is it a good way?
thanks a lot
RaviKishore.
Well, there are probably better solutions. But, both the Task Manager and the Performance Monitor will help you a great deal with finding memory and resource (handles, gdi etc.) leaks.Quote:
can we efficiently find the memory leaks through task manager?
is it a good way?
- petter
I've heard that both firefox and opera have memory leaks.
I used both programs and i do agree that sometimes too many tabs are open at the same time, the memory will spike to the top.
Anyone have the same experience with me or am the only one?
What actually causes memory leaks?
From what i know: using malloc() without ending it with free()
Any other causes?
Here are few combinations:
- malloc - free
- new - delete
- VirtualAlloc - VirtualFree
- HeapAlloc - HeapFree
- LocalAlloc - LocalFree
- GlobalAlloc - GlobalFree
Improper use of constructors and destructors
Can you give a single example for CTOR/DTOR implications, without putting the memory allocation/de-allocation stuff?? :rolleyes:Quote:
Originally Posted by Emiene
Can you show me how can this cause a problem?Quote:
Originally Posted by Ajay Vijay
I have some experience with Java, and the "new" is used for defining new objects of a class. I think it is used for the same purpose in Visual C++ (correct me if i'm wrong). But in Java, i never see the need to "delete" after "new". Is it because Java does garbage collection and cleanup by itself while visual C++ doesn't?
Absolutely. Java has its Runtime environment called JVM.Quote:
I have some experience with Java, and the "new" is used for defining new objects of a class. I think it is used for the same purpose in Visual C++ (correct me if i'm wrong). But in Java, i never see the need to "delete" after "new". Is it because Java does garbage collection and cleanup by itself while visual C++ doesn't?
C++ does NOT have anything as such. The runtime environment is the OS (unless it is attached to debugger, in that case Debugger is actually RTE).
You have to delete the memory yourself. This is one of the reason why C/C++ gives manifold performance over Java and other "runtime needed" languages like C#, VB.NET etc.
You'll find thousands of articles on the Internet about Java and C++ differences.