From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Schmidt <michael.a.schmidt@email.de>
Cc: 45651@debbugs.gnu.org
Subject: bug#45651: Aw: Re: bug#45651: 28.0.50; emacs native-comp crashes with pidigits bench
Date: Wed, 06 Jan 2021 20:44:51 +0000 [thread overview]
Message-ID: <xjfk0spdccc.fsf@sdf.org> (raw)
In-Reply-To: <trinity-af765b33-13d6-4bdc-ac87-eceeafe23686-1609875022209@3c-app-webde-bap12> (Michael Schmidt's message of "Tue, 5 Jan 2021 20:30:22 +0100")
Michael Schmidt <michael.a.schmidt@email.de> writes:
> Hi Andrea,
>
> [here an extended version with cc to 45651@debbugs.gnu.org]
>
> Clean build with
>
> emacs-8ad983c4acef60a80e8d6b6ba891b1ef957f2d7c.tar.gz
>
> Fedorea 33 VirtualBox 24GB+10GB swap: pidigits passed with ~61% peak memory consumption.
> Fedorea 33 VirtualBox 16GB+10GB swap: pidigits passed with ~98% peak memory consumption.
> Fedorea 33 VirtualBox 8GB +10GB swap: pidigits crashed as described before. Please no "Eight gigabytes of memory and
> constantly swaping" ;-)
> dmesg unchaged after boot, no further info.
>
> A build without nativecomp passed pidigits with ~1.5% memory consumption.
> Really looks like a memory leak.
Yeah I think this is a bug in the benchmark. This is compiled at speed
3 and the programmer should be responsible to "garbage-collect-maybe" in
hot loops if this is required.
If this theory is correct you should see the issue disappearing adding
~(declare (speed 2))~ to `elb-pidigits'.
Andrea
next prev parent reply other threads:[~2021-01-06 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 11:37 bug#45651: 28.0.50; emacs native-comp crashes with pidigits bench Michael Schmidt
2021-01-04 16:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-05 19:30 ` bug#45651: Aw: " Michael Schmidt
2021-01-06 20:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-15 20:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfk0spdccc.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45651@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=michael.a.schmidt@email.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).