Bug 2109473

Summary: When install emacs-common-ess, emacs crashes the system when it starts.
Product: [Fedora] Fedora Reporter: Nick Urbanik <nicku>
Component: emacs-common-essAssignee: José Matos <jamatos>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: alex, edgar.hoch, htl10, jamatos
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-03 01:24:56 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 Nick Urbanik 2022-07-21 10:33:56 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nick Urbanik 2022-07-21 10:38:00 UTC
My description disappeared.

After emacs-ess is installed, emacs starts, is unresponsive, consumes all resources till the computer is unusable.

Many processes are forked: here is just one process description from top:

/usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-64656c6574652d63686172_delete_char_0-i83seT.el

Comment 2 Hin-Tak Leung 2022-07-24 01:58:47 UTC
It is not a hang - my filing is more accurate:

https://bugzilla.redhat.com/show_bug.cgi?id=2109745

emacs spawns multiple child processes, and if you notice it early enough, you can do 'kilall emacs' in a different terminal window to recover. I have a CPU monitor gnome extension running, so it was obvious for me that emacs 28 was misbebaving, way before all the multiple child processes eat up all resources, and eventually leads to hangs for other people. It did not hang for me, because I noticed it and killed it. It is not a hang. 

There are mulitple filings upstream at ess github.

Comment 3 Hin-Tak Leung 2022-12-25 18:22:05 UTC
bug-fix emacs upgrade for this at https://bugzilla.redhat.com/show_bug.cgi?id=2109745#c27 .

Comment 4 Fedora Update System 2022-12-31 21:08:20 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:04 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:07 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:14 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 Fedora Update System 2023-01-03 01:24:56 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 9 Edgar Hoch 2023-01-04 13:00:57 UTC
I still get

Warning (comp): /usr/share/emacs/site-lisp/ess/ess-r-package.el: Error: Wrong number of arguments (3 . 4)

emacs-ess-18.10.2-6.fc36.noarch (on Fedora 36 and 37)

Comment 10 Fedora Update System 2023-01-11 01:34:35 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.