Opened 13 years ago
Closed 13 years ago
#8499 closed bug (invalid)
memory not being released ?
| Reported by: | grimus | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Kernel | Version: | R1/Development |
| Keywords: | memory | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
Desription 1 Doing a 'jam -q haiku-image' build after the ......patience ..... messages memory is not relaesed and system memory usage during the build is shown as 412M. Released after the build completes. Same build on an old image '40639' the memory is released before the build starts and is only 150M used during the build.
Description 2 After boot, 120M is shown used and if you monitor memory usage it does not change after a few seconds. No system activity seems to be taking place. Old system only 70M used a few seconds after boot and you can see memory usage changing all the time as system activity works in the background. No running programs apart from system. Using Process Controler to monitor memory.
Sorry if not clear descriptions, just ask for more info.
nightly hrev 44058 gcc2 hybridy 512M with 500M virtual memory.
Regarding your use case 1, jam really takes that much memory and it doesn't terminate until the build is done.
Regarding your use case 2, the memory statistics computation was incorrect. It was fixed in hrev43258.