38946ff82f
Not all platforms can properly release memory allocated via platform_allocate_region() at present; in particular the BIOS loader seems to (at least partially) leak it. And due to how the kernel args ranges are handed off to the kernel, it seems allocated physical pages that aren't virtually mapped are leaked at present as well. That seems like a bug that we should likely fix, and moreover the heap shouldn't use that facility at all (but instead request bootloader-local memory if possible; on the BIOS loader that will ultimately go through similar logic, but on e.g. EFI it will be entirely separate.) But in the meantime, we can just increase the size of the "large allocation" threshhold so that packagefs temporary buffers (of 64 and 93 KB) stay on the main heap, and don't hit that facility at all. The "maximum boot loader heap usage" seems to go up by about ~200 KB with this change (e.g. 588 KB -> 797 KB), so increase the default heap size by 256 KB to compensate. This fixes most of the rest of #14831: memory usage after the boot has finished is down by over 100 MB (!). The remaining problems and leaks can be dealt with in later changes. |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.