Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.c Subject: Re: realloc() - frequency, conditions, or experiences about relocation? Date: Tue, 25 Jun 2024 07:06:41 -0000 (UTC) Organization: A noiseless patient Spider Lines: 10 Message-ID: References: <875xtyu0kk.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 25 Jun 2024 09:06:41 +0200 (CEST) Injection-Info: dont-email.me; posting-host="250b38e1e4730787d8a829a06e323428"; logging-data="1524803"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/BpcorlTT9w2x8WCInWzSM" User-Agent: Pan/0.158 (Avdiivka; ) Cancel-Lock: sha1:Y2kUbUVXf2vvvqpAaGkuvCuMYyI= Bytes: 1678 On Mon, 24 Jun 2024 18:50:15 +0100, Malcolm McLean wrote: > Baby X has bbx_malloc() which is guaranteed never to return NULL ... Does it actually allocate the (physical) memory? I wrote a memory-hog app for Android once, and found that allocating large amounts of memory space had very little impact on the system. Then when I added code to actually write data into those allocated pages, that’s when it really started to break into a sweat ...