X-Spam-Check-By: sourceware.org Message-ID: X-Sender: emacs_user AT hotmail DOT com From: "emacs user" To: cygwin AT cygwin DOT com Subject: Re: memory problems with cvs gnu emacs on latest cygwin Date: Thu, 03 Aug 2006 23:00:32 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 >From: Reini Urban >emacs user schrieb: > > I have reported this problem to the gnu emacs developers a few >times, but it seems that emacs is not actively maintained for cygwin >right now. perhaps someone here can help? I am happy to provide more >details if needed. thanks... > > A brief problem description: > > memory usage of emacs does not decrease after killing buffers >with images. > > >This is lisp (emacs lisp), so it's a feature not a bug. thanks for responding, although this is incorrect, please see below. > > emacs.exe -q --no-site-file& > the memory usage right after startup is 14912; > after editing a small image: 16452; > after killing the buffer with the image and using > M-:(clear-image-cache t)RET: 16476; after editing a large image: >39164; > again quit+clear cache: 34484; > edit small+medium+large images: 58936; > quit+clear: 87636... (increased!) > > >overall memory usage in most lisp's doesn't decrease on released > objects. memory usage is reclaimed when the garbage collector > starts its walk, which happens when there's not enough memory. > that's actually not true. the simple observation is that the bug I describe does not occur on other platforms such as gnu/Linux. memory is returned to the operating system after the buffer is killed. best, EU _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ -- 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/