emacs crash when run under terminal with 'emacs -nw' #1170
Comments
|
Does the issue go away if your remove liberime from your config? |
|
always crash, this is my private doom config. https://github.com/shuxiao9058/doom-emacs-private With |
|
Does it work with your private config disabled? e.g. mv ~/.doom.d ~/.doom.d.old
mkdir ~/.doom.d
cp ~/.doom.d.old/init.el ~/.doom.d/init.el
emacs -nw |
@hlissner The same error. |
|
I'm stumped and cannot reproduce this. Have you tried reinstalling emacs-plus? |
|
yes,the same when reinstall emacs-plus or install emas. |
|
It was caused by |
hlissner
added
module:ui/doom-dashboard
|
I've made some changes to the dashboard in f934f38. When you have some time, could you update and let me know if that resolves your segfaulting issue? |
thee same error.
```
Process: Emacs [1711]
Path: /usr/local/Cellar/emacs-plus/HEAD-8b2dad2/Emacs.app/Contents/MacOS/Emacs
Identifier: Emacs
Version: Version 27.0.50 (9.0)
Code Type: X86-64 (Native)
Parent Process: zsh [1232]
Responsible: Emacs [1711]
User ID: 501
Date/Time: 2019-04-09 12:17:19.086 +0800 Sleep/Wake UUID: 515BC712-ACB4-436A-A75E-BC7B3D5C8D37 Time Awake Since Boot: 42000 seconds System Integrity Protection: disabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGABRT) VM Regions Near 0x40: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3:: gmain Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 0 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Model: MacBookPro11,3, BootROM 151.0.0.0.0, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12 |
|
@hlissner It works fine with emacs 26.2 now. |
Potentially addresses crashing issues caused by the dashboard. Relevant to #1170
|
this is backtrace |
hlissner
added
status:unknown
|
I got the same issue on 27.0.50 when using from terminal. This happens on my personal config which is not doom. I narrowed to the package that causes it. Commenting EDIT: Calling magit-status crashes emacs 27.0.50 in terminal. EDIT: magit alone works fine. But with git-gutter it crashes. Seems like git-gutter is the issue |
|
I'm stumped. I'm half-convinced this has to do with a faulty build of Emacs (particularly 27 on MacOS) -- I cannot reproduce it on any of my systems, Linux or MacOS, and reports of these crashes seem to cover a wide area. Most of these reports appear to be related to functionality that manipulates the fringes or margins (which git-gutter, org-indent-mode, the Doom dashboard and magit-status all deal with). |
|
@hlissner Any plan to deal with this issue? |
|
@shuxiao9058 No. I don't understand the cause. I cannot reproduce it. It seems to be a Emacs 27-only issue, as well. No surprise bleeding edge Emacs will have bugs. Until (and if) I find a way to reproduce it, I suggest using 26.1/26.2 instead. |
|
I am using 26.2 right now. Emacs 27 is not stable with terminal. I was having random crashes with 27 on using daemon/frames. |
|
Is this still an issue? |
|
yes |
|
In order to reproduce this, you needs emacs I built emacs 27 in a pretty straight-forward way, I cloned the source from Savannah, ran |
hlissner
added
module:ui/vc-gutter
|
@spudlyo That is odd. The fringe should be disabled in tty Emacs. What does It's possible that the NS build tests for the existence of the (when (fboundp 'define-fringe-bitmap)
(fmakunbound 'define-fringe-bitmap)) |
|
So
|
hlissner
added
status:resolved-elsewhere
|
@spudlyo Makes sense. Thanks so much for looking into it! |
|
This was fixed upstream, and I can no-longer reproduce the crash after recompiling from master. I think you can close this one! |
hlissner
added
the
status:resolved-elsewhere
|
always crash...
|
|
Heya @shuxiao9058, the initial upstream fix for this didn't quite nail it 100%. Robert Pluim pushed a better fix for this today in commit |
error run on iTerm with 'emacs -nw'
as d12frosted/homebrew-emacs-plus#112
The text was updated successfully, but these errors were encountered: