From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: (heap 1024 82721 1933216)
Date: Sat, 18 Jan 2014 06:12:49 -0800 [thread overview]
Message-ID: <52DA8BE1.5090702@dancol.org> (raw)
In-Reply-To: <83k3dxjsd2.fsf@gnu.org>
On 01/18/2014 06:07 AM, Eli Zaretskii wrote:
>> Date: Sat, 18 Jan 2014 05:51:26 -0800
>> From: Daniel Colascione <dancol@dancol.org>
>> CC: emacs-devel@gnu.org
>>
>> On 01/18/2014 05:50 AM, Eli Zaretskii wrote:
>>>> Date: Sat, 18 Jan 2014 05:39:30 -0800
>>>> From: Daniel Colascione <dancol@dancol.org>
>>>>
>>>> On Emacs trunk, I recently got into a situation where Emacs had a vsize
>>>> of over 6GB. After killing all buffers, garbage-collect reported (heap
>>>> 1024 82721 1933216) as the most interesting part of its on its return
>>>> value. dlmalloc's free memory retention seems a bit severe here. Are we
>>>> just badly fragmenting the heap?
>>>
>>> Buffers are not allocated off the heap, as you well know.
>>
>> No, but their buffer locals might be.
>
> I find it hard to believe that buffer locals could devour gigabytes of
> memory, no matter what fragmentation did we cause.
I agree and never said they were --- I was just trying to eliminate as
many GC roots as possible. Anyway, that's not the point: there's still
2GB of accounted memory sitting there unused.
next prev parent reply other threads:[~2014-01-18 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 13:39 (heap 1024 82721 1933216) Daniel Colascione
2014-01-18 13:50 ` Eli Zaretskii
2014-01-18 13:51 ` Daniel Colascione
2014-01-18 14:07 ` Eli Zaretskii
2014-01-18 14:12 ` Daniel Colascione [this message]
2014-01-18 17:17 ` Eli Zaretskii
2014-01-18 14:15 ` David Kastrup
2014-01-18 17:19 ` Eli Zaretskii
2014-01-19 2:53 ` Stefan Monnier
2014-01-19 3:31 ` Daniel Colascione
2014-01-19 4:19 ` Stefan Monnier
2014-01-19 4:24 ` Daniel Colascione
2014-01-19 14:37 ` Stefan Monnier
2014-01-19 15:45 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52DA8BE1.5090702@dancol.org \
--to=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.