Autosave: 2024-04-20 14:10:04
This commit is contained in:
parent
f6628a0a4e
commit
a4a0cfffa8
2 changed files with 12 additions and 4 deletions
BIN
.zk/notebook.db
BIN
.zk/notebook.db
Binary file not shown.
|
@ -7,9 +7,17 @@ created: Saturday, April 20, 2024
|
||||||
|
|
||||||
# Heap memory
|
# Heap memory
|
||||||
|
|
||||||
## Summary
|
Along with [[Stack_memory|Stack memory]], programs make use of _heap memory_
|
||||||
|
during runtime.
|
||||||
|
|
||||||
- Along with [[Stack_memory|Stack memory]], programs make use of _heap memory_
|
Heap memory does not use a standardised data structure and can be accessed from
|
||||||
during runtime.
|
any point within the program.
|
||||||
|
|
||||||
- [ ] ## Related notes
|
Whereas stack memory with it's LIFO structure has memory management built-in
|
||||||
|
when programs allocate memory from the heap they must manually deallocate it
|
||||||
|
when it is no longer required. This process of "freeing memory" is known as
|
||||||
|
_garbage collection_. In a language like C, this is the explicit concern of the
|
||||||
|
programmer and is not abstracted away. Failure to properly manage garbage
|
||||||
|
collection is what causes [[Memory_leaks]].
|
||||||
|
|
||||||
|
## Related notes
|
||||||
|
|
Loading…
Add table
Reference in a new issue