You also may be given a false impression of a memory leak if you’re using Windows Task Manager to monitor memory usage, as by default it shows the current Working Set size of a process instead of the actual in-use memory or size of its address space.
Memory usage will also grow regularly over time when an application first starts up as various libraries and APIs initialize static storage and other stuff they need. To be sure you’ve really encountered a leak you should run your application for at least 30-60 seconds and perform the suspect operation as much as possible, to be certain that the memory usage increase you’re seeing is a direct result of the operation.
- Janus answered 11 years ago
well if the question is ‘do you know’ then no, because there is no memory allocation, unless maybe it is a codec that isnt written by us. Is it ogg or wma? It wouldnt be leaking anyway, it is probably just expanding until the song is released. That is not a leak. A leak is when you free the sound and the memory is still there.
Please login first to submit.