[haiku-development] Re: Weird memory behaviour.
- From: Bruno Albuquerque <bga@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 24 Jul 2008 10:37:25 -0300
Bruno Albuquerque wrote:
#include <unistd.h>
int main(void) {
char* test - new char[1024 * 1024 * 500]
sleep(5); // Give some time so AM can pick the change.
// Intentionally leak allocated memory.
}
On a related note, if I change the above program to allocate 850 Mb (I
am running VMWare with 1 Gb of available memory for Haiku) it will crash
with a segmentation fault in add_fdes() (inside libroot, it seems)
instead of simply bailing out with an out of memory error.
-Bruno
- Follow-Ups:
- [haiku-development] Re: Weird memory behaviour.
- From: Rene Gollent
- References:
- [haiku-development] Weird memory behaviour.
- From: Bruno Albuquerque
Other related posts:
- » [haiku-development] Weird memory behaviour.
- » [haiku-development] Re: Weird memory behaviour.
- » [haiku-development] Re: Weird memory behaviour.
- » [haiku-development] Re: Weird memory behaviour.
#include <unistd.h>
int main(void) {
char* test - new char[1024 * 1024 * 500]
sleep(5); // Give some time so AM can pick the change.
// Intentionally leak allocated memory.
}
- [haiku-development] Re: Weird memory behaviour.
- From: Rene Gollent
- [haiku-development] Weird memory behaviour.
- From: Bruno Albuquerque