#3807 closed enhancement (fixed)
Computer unceremoniously reboots when exceeding Virtual Memory
| Reported by: | haiqu | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | System/Kernel | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
In hrev2046 I mentioned that the message given when running out of physical memory (vfork() error) was a bit cryptic. When you reach the end of Virtual Memory it's worse - the computer simply reboots.
To test this, use a computer with < 640Mb memory and try to build the source tree within Haiku, using a VM size of about 500Mb or less.
Friendly messages about available memory being almost exceeded would be great.
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 9 years ago
Sorry, didn't see this until today. I do still have a PC with that little memory but it's in storage 1,647km away. :-)
comment:3 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This is now fixed, it seems. Applications may crash due to malloc returning NULL, but the OS does not segfault.
comment:5 by , 4 years ago
| Milestone: | R1 → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Could you check with a current revision please ?