help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Emacs and nxml/nxhtml-mode: memory overflow


From: Martin Butz
Subject: Emacs and nxml/nxhtml-mode: memory overflow
Date: Thu, 23 Aug 2012 14:56:26 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081125 Thunderbird/2.0.0.18 Mnenhy/0.7.5.0

Hi,

since a few weeks I have some serious problem, while using emacs for webdevelopement. I use (and would like to in future) nxhtml-mode. It seems that this mode (or the underlying nxml-mode) causes emacs to consume 100 % cpu-power - at least after a while. I can not spotify the exact reason for this; in some cases it seem to be caused be validation. Emacs says MEM FULL! (mode line), freezes and there's no other way as to kill the process.

I setup a separate .emacs-webdev to use emacs for webdevelopement without allmost any of my extensions/configuration, which I usually use. This did work for a while, but as I had a crash today, it seems, that it can happen anytime.

There might be some side effects concerning one or the other extension but I have no clue how I can find out whats going on. It could also be caused by some bug in nxhml/nxhtml-mode but I can not find any information on the web, which seems to backup this.

I already filed a bug report at launchpad (which admittedly is based on a very poor information base, as I do not know how to securely reproduce the misbehaviour); also my posting at stackoverflow [2] was not crowned with success.

Currently I use emacs 23.2.1 on Linux Mint 11. The last version of nxml-mode I used is 20041004.

Any tips about that? How can I possibly find out, what emacs causes to do that?

Greetings
Martin

[1] <https://bugs.launchpad.net/nxhtml/+bug/1032564>
[2] <http://stackoverflow.com/questions/11247666/emacs-nxhtml-mode-memory-full>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| G. Martin Butz, mb@mkblog.org, 0421 98749324, www.mkblog.org |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]