When evaluating the following codeblock with babel from org-mode: Emacs closes abruptly and displays a "Segmentation fault" error: The expected behavior was no fault whatsoever. The error seems to depend on the webpage, presumably because of the text content. I am using Debian Jessie 8.5. The only configuration in my .emacs file is: To allow codeblock evaluation.
Alef Farah <afarah@inf.ufrgs.br> writes: Did you happen to (or could you) test in a console emacs i.e. from "emacs -nw"? I suspect that might avoid the crash, but it'd be nice to know. And in case this is a transient content issue, it might also be helpful if you could attach an out.html that causes the crash. Thanks
Rob Browning <rlb@defaultvalue.org> writes: I just tested from X as the vagrant user on a fresh, updated debian/jessie64 (8.5) vagrant box after (roughly): vagrant init debian/jessie64 vagrant up vagrant ssh sudo su - apt update apt install emacs xinit xterm xmonad xinput exit Using the .emacs you posted, and didn't see a crash. I wonder what else might be relevant. Thanks
I tested with -nw and it does not crash. After that I opened the file with the GUI and it instantly crashed (the results of the codeblock execution were now displayed on the file, since it was successfully evaluated when using -nw). The contents are quite large. I am attaching the problematic file. I noticed that if I open the file with emacs' GUI in a small window, such that the problematic text is not displayed, emacs does not crash. Emacs only crashes when it attempts to display the text. I tried opening the file with another graphical application (namely Iceweasel) and it did not crash.
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to send a complete, minimal example to the Emacs developers using M-x report-emacs-bug.
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to send a complete, minimal example to the Emacs developers using M-x report-emacs-bug.