Emacs consistently crashes

[snogglethorpe]

I use emacs, installed using pkg, in Termux a lot, and it crashes really often. Sometimes I can get a few hours use out of it, sometimes, it crashes after 30 seconds.

This is the error that it spits out to the terminal:
Fatal error 11: Segmentation faultidSegmentation fault (core dumped)

I've never been able to identify a particular activity I'm doing inside emacs, it just seems to happen kind of randomly.

I suppose the right thing to do is build emacs from source, so I can run a debugger on it and see what's happening.... but I'm a little scared to do that on my poor little chromebook with not so much flash disk....

I've asked about this on the Termux "gitter" chat, and nobody else seems to have seen the same behavior. Maybe it's related to the system type? [I'm using a Chromebook with an x86-style CPU.]

[Note that emacs is still useful, it's very good at recovering your edits after a crash, and generally these crashes happen infrequently enough that they're mostly just a nuisance...]

Steps to reproduce
Hard to be helpful, but: use emacs a lot, wait for it to crash.

Expected behavior
Not crashing.

Additional information
Updatable packages:
apt/stable 1.4.9-19 i686 [upgradable from: 1.4.9-15]
bash/stable 5.0.11 i686 [upgradable from: 5.0.9]
binutils/stable 2.33.1 i686 [upgradable from: 2.32-5]
ca-certificates/stable 20191016 all [upgradable from: 2019051]
clang/stable 9.0.0 i686 [upgradable from: 8.0.1]
command-not-found/stable 1.42 i686 [upgradable from: 1.39]
coreutils/stable 8.31-8 i686 [upgradable from: 8.31-7]
curl/stable 7.66.0-1 i686 [upgradable from: 7.65.3-6]
dos2unix/stable 7.4.1 i686 [upgradable from: 7.4.0-1]
emacs/stable 26.3-1 i686 [upgradable from: 26.3]
findutils/stable 4.7.0 i686 [upgradable from: 4.6.0-4]
gdb/stable 8.3.1 i686 [upgradable from: 8.3-4]
glib/stable 2.60.7 i686 [upgradable from: 2.60.6-1]
gnutls/stable 3.6.10 i686 [upgradable from: 3.6.9-1]
libandroid-support/stable 25-2 i686 [upgradable from: 25-1]
libcurl/stable 7.66.0-1 i686 [upgradable from: 7.65.3-6]
libexpat/stable 2.2.9 i686 [upgradable from: 2.2.7-1]
libffi/stable 3.2.1-5 i686 [upgradable from: 3.2.1-4]
libgcrypt/stable 1.8.5 i686 [upgradable from: 1.8.4-1]
libgnutls/stable 3.6.10 i686 [upgradable from: 3.6.9-1]
libllvm/stable 9.0.0 i686 [upgradable from: 8.0.1]
m4/stable 1.4.18-3 i686 [upgradable from: 1.4.18-1]
ncurses/stable 6.1.20190928 i686 [upgradable from: 6.1.20190511-7]
ndk-sysroot/stable 20-6 i686 [upgradable from: 20-1]
openssh/stable 8.1p1 i686 [upgradable from: 8.0p1-4]
openssl/stable 1.1.1d-1 i686 [upgradable from: 1.1.1c-2]
strace/stable 5.3 i686 [upgradable from: 5.2]
termux-tools/stable 0.72 all [upgradable from: 0.69-2]
texinfo/stable 6.7 i686 [upgradable from: 6.6-1]
Subscribed repositories:
https://dl.bintray.com/grimler/science-packages-24 science/stable
https://dl.bintray.com/grimler/game-packages-24 games/stable
https://dl.bintray.com/termux/termux-packages-24 stable/main
System information:
Linux localhost 3.18.0-19747-gd0dcdfafc1b5 termux/termux-app#1 SMP PREEMPT Mon Oct 21 01:01:50 PDT 2019 i686 Android
Termux-packages arch:
i686
Android version:
9
Device manufacturer:
Google
Device model:
Samsung Chromebook Pro

[Grimler91]

Sounds like a duplicate of #2599, but you are on i686 and not arm. It would be great if you could try getting a gdb backtrace by:

• Update all your packages with pkg upgrade
• Download and install this i686 debug build of emacs: https://grimler.se/emacs-dbg_26.3-1_i686.deb
• Create a file with a couple of hundred lines
• Run gdb --ex run --args emacs your-file and then scroll up and down until a crash happens (scrolling seems to be a fairly fast way to trigger a crash)
• When you have gotten the seg fault, run backtrace in gdb to (maybe) see where the crash comes from

[snogglethorpe]

Ok, I did that... the results don't seem too useful, but:

System information:  Program received signal SIGSEGV, Segmentation fault.
(gdb) ba
#0  0xf7913ba3 in sigsetjmp () from /system/lib/libc.so
Backtrace stopped: Cannot access memory at address 0x40998b46

[ghost]

Seems exact duplicate of #2599.
Someone even already reported that it has problems on chromebooks too #2599 (comment).

[snogglethorpe]

Maybe that other issue should be renamed to remove "arm" from the title?

[ghost]

remove "arm" from the title?

Done.