GNU bug report logs -
#48807
[master][windows10] emacs hangs when editing *.xml files
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 48807 in the body.
You can then email your comments to 48807 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#48807
; Package
emacs
.
(Thu, 03 Jun 2021 08:15:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Édouard Debry <edouard.debry <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 03 Jun 2021 08:15:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
- emacs master (a few weeks)
- compiled with native-comp on windows 10 with latest mingw64
environment
* Bug description
- open an *xml file, the nxml-mode is enabled in the buffer.
- edit (modify, save changes) the *xml file
- within a few minutes, emacs hangs by consuming the whole ram
(not cpu).
As a consequence, windows 10 becomes much less responsive
That is to note, this issue does not occur if I do noy modify the
*xml file.
I checked on windows 10 that it is precisely emacs which eats all
memory, not one of its child processes.
I am not 100% sure yet, but it does not seem platform
(windows,linux) related.
I googled "emacs xml hangs", some similar issues have already been
reported, but I could not find any fixes or workaround.
The only workaround so far I found is to quickly edit xml files,
save and close them
before emacs begins to eat all memory.
Regards
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#48807
; Package
emacs
.
(Thu, 03 Jun 2021 08:31:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 48807 <at> debbugs.gnu.org (full text, mbox):
> From: Édouard Debry <edouard.debry <at> gmail.com>
> Date: Thu, 03 Jun 2021 10:14:10 +0200
>
> - emacs master (a few weeks)
Please try the latest master and see if the same problem happens
there.
> - compiled with native-comp on windows 10 with latest mingw64
> environment
Which GCC version does that come with? And which version of libxml?
> * Bug description
> - open an *xml file, the nxml-mode is enabled in the buffer.
> - edit (modify, save changes) the *xml file
Does this happen to you with _any_ XML file, or just with some? If
the latter, can you post one such file?
> - within a few minutes, emacs hangs by consuming the whole ram
> (not cpu).
> As a consequence, windows 10 becomes much less responsive
Does Emacs run asynchronous native-compilation sub-processes when this
happens? If so, how many such sub-processes are running, and what
happens if you kill some or all of them?
> The only workaround so far I found is to quickly edit xml files,
> save and close them
> before emacs begins to eat all memory.
Please use the Task Manager or (better) Process Explorer to find out
which of the Emacs processes consumes most of the memory. Is that the
process you started or any sub-processes that native-compile Lisp
files in the background? How much memory does each Emacs consume?
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 04 Jun 2021 10:00:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#48807
; Package
emacs
.
(Fri, 02 Jul 2021 11:15:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 48807 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> The only workaround so far I found is to quickly edit xml files,
>> save and close them
>> before emacs begins to eat all memory.
>
> Please use the Task Manager or (better) Process Explorer to find out
> which of the Emacs processes consumes most of the memory. Is that the
> process you started or any sub-processes that native-compile Lisp
> files in the background? How much memory does each Emacs consume?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If more progress can be made,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
48807 <at> debbugs.gnu.org and Édouard Debry <edouard.debry <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 02 Jul 2021 11:15:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 30 Jul 2021 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 270 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.