X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Krzysztof Duleba Subject: Re: malloc/new allocate twice as much? Date: Sat, 31 Dec 2005 02:23:20 +0100 Lines: 16 Message-ID: References: <001e01c60d96$82fc34e0$43055f12 AT somerville> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) In-Reply-To: <001e01c60d96$82fc34e0$43055f12@somerville> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dan Stratila wrote: > This is an issue I've discovered and reproduced while trying to compile > polymake (see the thread "gcc crash (memory?)"). It seems that both malloc > and new allocate take up twice the amount of memory needed. > > I wrote a short program to allocate and use memory in chunks (mem-test.cpp), > and compiled it with g++ 3.4.4. I monitored it using the Windows Task > Manager. When asked to allocate 100MB in increments of 10MB, the process > size goes to 100MB and then drops to 0, as expected. However, the total > commit charge for the machine goes up by 200MB, and then drops back! Try the snapshot. On my laptop with XP SP2, 20051222 snapshot, 1GB RAM and 1GB swap file I had no problem allocating 1.8 GB. Krzysztof Duleba -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/