It's UWAweek 30 (2nd semester, week 1)

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 8 other people reading this forum.


 UWA week 42 (2nd semester, week 12) ↓
SVG not supported

Login to reply

👍?
helpful
1:43pm Tue 17th Oct, Christopher M.

ANONYMOUS wrote:
> Is the 7579 bytes that were not free'd a significant amount? Or should I go in and make sure to free all of the memory to have 0 bytes of leaked memory?
I have a great Algorithms textbook named Compared to What? - https://www.amazon.com.au/Compared-What-Introduction-Analysis-Algorithms/dp/071678243X/r Is 7579 bytes a lot? Compared to what? When any process terminates the operating system (naturally) reclaims its memory for (re)use by existing and future processes. If your program runs for a long time, such as server software that runs for weeks or months, then 7579 bytes would be significant if it was leaked for every transaction.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  7:24AM Jul 25 2024
Privacy policy