Emacs takes 100% CPU when adding a new line at the end of a file (with Evil and ProofGeneral running).

[Martin Constantino–Bodin]

Hi,
I’m not used with Emacs (I’m more a Vim user) but as it includes a module “ProofGeneral” to work with Coq, I was working on it. The “Evil” package was active too. Both of those package were installed throw “el-get”: there shouldn’t be any installation problem with my packages.
It seems that each time I’m going to the end and adding a new line on a Coq file, Emacs takes 100% of the CPU. I had to kill it each time (I’ve tested it several times on my Coq files).
I’ve just updated my system to Precise, but the bug was still there in Oneiric (here is the dupplicate bug report: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/988839).
I guess this is more due to “proofGeneral”, but I’m not sure of it.
Martin.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: emacs23-nox 23.3+1-1ubuntu9
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 01a18e0a74cbde3d34a62f62830ed079
CheckboxSystem: f134069bba098730d27f59b402920826
Date: Tue May 8 00:42:40 2012
ExecutablePath: /usr/bin/emacs23-nox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: emacs23
UpgradeStatus: Upgraded to precise on 2012-05-07 (0 days ago)

[Sasa Paporovic (melchiaros)]

Hi Martin,

the problem is that proffgeneral is in the universe repositories. So, there will be no bughandling from the core developers.

In such cases we tend to bring up such bugs upstream to the original developers.

And there we have the next problem. Developers of emacs are not happy to get reports from not the very latest packages. And the very latest are on Quantal(emacs 24.x and not on Precise(emacs23.x).

The strange variant where a pre upgrade to quantal:

https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha2

but this is dangerous for your data(you may use dejadup for backup first - but backup in any way!). It may render your system unbootable.

The second option is virtualisation.

I give you a short howto(it is a standard text):

Could you(someone) try to reproduce on a Ubuntu12.10 developer version with testdrive-gtk or virtualbox4.1.18 and report back?

-----------------------------------------------

Both are Virtualisation programs and let you run Ubuntu12.10 as a normal program without touching your computer operating system.

See for details:

http://en.wikipedia.org/wiki/Virtual_machine

-----------------------------------------------

testdirve-gtk is in the main repositories and available for installation by default on Ubuntu systems. The download, installation and starting of the virtualmachine of the newest Ubuntu version 12.10 can be handled within testdrive.

virtualbox4.1.18 could be installed from:

https://launchpad.net/~debfx/+archive/virtualbox

The Ubuntu12.10 installation media must downloaded manually for virtualbox and could be downloaded from:

http://cdimage.ubuntu.com/daily-live/current/

[Sasa Paporovic (melchiaros)]

I suggest you to use testdrive. It is slow, but easy to use.

When you have done and the bug is still there in quantal, please set the status of the report back to new and report.

In this case we bring the problem upstream.

When it is gone in quantal, we try to bring the emacs 24 version as backport to precise.

[Launchpad Janitor (janitor)]

[Expired for emacs23 (Ubuntu) because there has been no activity for 60 days.]