Bug 2109717

Summary:	emacs (emacs-ess) freezes system
Product:	[Fedora] Fedora	Reporter:	Peter L. Hurd <phurd>
Component:	emacs	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	36	CC:	dan.cermak, dueno, gordon.messmer, jkeating, jonathan.underwood, msekleta, phracek, rlm, robinlee.sysu, swt
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	emacs-28.2-1.fc37 emacs-28.2-1.fc36	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-03 01:24:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter L. Hurd 2022-07-21 21:55:24 UTC

Description of problem:
launching emacs (emacs-28.1-2.fc36.x86_64) with emacs-ess installed (emacs-ess-18.10.2-6.fc36.noarch), the echo area (?) seems to hang on the message:
Loading /usr/share/emacs/site-lisp/siate-start.d/ess-init.el (source)
cpu usage pegs, with top reporting many emacs processes before kswapd0 becomes top process.

On my Lenovo X1 carbon the system then freezes requiring a hard power off, on my Lenovo X395 the volume widget dies then the shell crashes logging me out of the gui.

Nothing like this happened before yesterday's upgrade of emacs to emacs-28.1-2.fc36.x86_64, downgrading emacs fixes the problem (downgrades to emacs-1:27.2-9.fc35.x86_64).

Version-Release number of selected component (if applicable):
emacs-28.1-2.fc36.x86_64
emacs-ess-18.10.2-6.fc36.noarch

How reproducible:
2/2 computers I tried...

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rob McMillin 2022-10-11 15:16:59 UTC

This generates a fork bomb.

It's utterly unbelievable that this shipped in this state.

Comment 2 Rob McMillin 2022-12-12 16:30:38 UTC

Now it looks like they did not provide a downgrade path for emacs 27 in Fedora 37.

Comment 3 Rob McMillin 2022-12-13 01:37:16 UTC

It looks like this has maybe been fixed in 1:28.2+1-3, but 

https://groups.google.com/g/linux.debian.bugs.dist/c/QdejQ-bm-rU?pli=1

Comment 4 Fedora Update System 2022-12-31 21:08:23 UTC

FEDORA-2022-e37f239f2e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e37f239f2e

Comment 5 Fedora Update System 2022-12-31 21:10:06 UTC

FEDORA-2022-d69c7f95a4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d69c7f95a4

Comment 6 Fedora Update System 2023-01-01 01:52:09 UTC

FEDORA-2022-d69c7f95a4 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d69c7f95a4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d69c7f95a4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-01-01 02:00:16 UTC

FEDORA-2022-e37f239f2e has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e37f239f2e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e37f239f2e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Rob McMillin 2023-01-01 02:21:14 UTC

Thanks, guys.

Comment 9 Fedora Update System 2023-01-03 01:24:58 UTC

FEDORA-2022-d69c7f95a4 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-01-11 01:34:37 UTC

FEDORA-2022-e37f239f2e has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.