RE: Memory Leaks
"Mike Watson" <[email protected]>
| Newsgroups | gmane.comp.programming.cppug |
|---|---|
| Message-ID | <[email protected]> |
Hi Anthony, You would only fill up your hard drive if your program was writing out files of some type. Memory leaks would cause your application to crash because it has used up all the available memory (ram). 30 GIGS is a lot to lose, what kind of applications are you running? Do they deal with images? Try this: The first time you run your application in the day, do a search for files with the current time stamp. See what you program created/modified that day. Focus on files of large size. You may find a clue there. -m -----Original Message----- From: Anthony Marlow [mailto:[email protected]] Sent: Monday, May 17, 2004 3:41 PM To: [email protected] Subject: [cppug] Memory Leaks I'm new to programming, and I've been using C++ a lot, mostly doing example projects from a book that I bought. But somehow, since I started programming, just a little over a month ago, I've lost about 30 GB of space from my hard drive, and I can't figure out where it has gone. Is it possible that I've had some kind of memory leak, and that has filled up my hard drive? How can I verify what is taking up so much space on the hard drive? And if it is from memory leaks, how do I get rid of it? I've already done the usual disk maintanence stuff, like defrag and scan and disk clean-up, but nothing has worked. I'd really appreciate any help that I can get on this! Thanks so much, Marlow Yahoo! Groups Sponsor ADVERTISEMENT click here <http://rd.yahoo.com/SIG=129tvbouf/M=295196.4901138.6071305.3001176/D=groups /S=1705006788:HM/EXP=1084911489/A=2128215/R=0/SIG=10se96mf6/*http://companio n.yahoo.com> _____ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/cppug/ * To unsubscribe from this group, send an email to: [email protected] <mailto:[email protected]?subject=Unsubscribe> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> .