unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: awrhygty@outlook.com
Cc: 69263@debbugs.gnu.org
Subject: bug#69263: 29.1; emacs freeze with memory swap
Date: Mon, 19 Feb 2024 14:41:58 +0200	[thread overview]
Message-ID: <86wmr0pqw9.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB3920433162F8A8A1036B1D4DC3512@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)

tags 69263 moreinfo
thanks

> From: awrhygty@outlook.com
> Date: Mon, 19 Feb 2024 14:56:10 +0900
> 
> 
> My PC has 8GB memory and HDD, no SSD.
> Emacs freezes with the procedure below.
> 
> (0) Close all applications.
> (1) Start task manager.
>     Confirm disk usage is low and memory usage is about 2GB or less.
> (2) Start emacs -Q
> (3) Evaluate the form below
>       (progn (make-string (* 8000 1000 1000) 0)
>              (kill-emacs))
> (4) Memory usage increases and then decreases in ten seconds.
> (5) Disk usage keep 100% active for a few minutes.
> (6) Application window of emacs keep alive and emacs process name is
>     displayed in the process tab of task manager.
>     (At least 10 hours, I waited.)

I don't have a 8GB 64-bit Windows system to try this, and the results
are likely to be dependent on the intimate details of the Virtual
Memory setup on that system.

So if you want to help us understand what happens in the strange case
where a Lisp program creates a 8GB Lisp string, and clear it all, on a
8GB MS-Windows system, please attach GDB to Emacs after running the
above recipe, and produce a backtrace that can be used to try to
figure out what happens.  (I hope that your Emacs binary is not
stripped of debugging symbols, because if it's stripped, GDB will not
tell anything useful.)

Thanks.





  reply	other threads:[~2024-02-19 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  5:56 bug#69263: 29.1; emacs freeze with memory swap awrhygty
2024-02-19 12:41 ` Eli Zaretskii [this message]
2024-02-20 13:33   ` awrhygty
2024-02-20 14:40     ` Eli Zaretskii
2024-02-20 15:33       ` awrhygty
2024-02-20 17:08         ` Eli Zaretskii
2024-06-09 20:56           ` Stefan Kangas

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=86wmr0pqw9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69263@debbugs.gnu.org \
    --cc=awrhygty@outlook.com \
    /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).