From: Tomasz Kowal <tomekowal@gmail.com>
To: 39164@debbugs.gnu.org
Subject: bug#39164: Reproducing SIGSEGV bug
Date: Sun, 26 Jan 2020 18:41:42 +0100 [thread overview]
Message-ID: <CABsLkmXeURtMRLkfJLVU=6WQfMRKnb1+Ssg3L9kau3y-=SVqAQ@mail.gmail.com> (raw)
In-Reply-To: <CALGYRRe9DUUpaPK0rH=sC7DwfObsH0rkasHP=cW0By24QXXWGA@mail.gmail.com>
Hi! I have a speculation to share.
In the project that produced SIGSEGV, I was using lsp-mode.
It asks if I want to "watch files" every time I open a project.
I added really high threshold for the number of allowed watched files
in .dir-locals.
Shortly after I encountered the SIGSEGV for the first time.
I now changed it back to not watching the files, and I am not
encountering the problem anymore.
In the Bug#39164 upstream:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39164, they also mention
lsp-mode.
I am not sure if that helps but I believe, enabling file watching in
lsp-mode on a big project consumes enough memory to make the bug more
likely to reoccur.
BR,
Tomasz Kowal
prev parent reply other threads:[~2020-01-26 17:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:00 bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems Justin Guenther
2020-01-17 21:01 ` Eli Zaretskii
2020-01-20 9:15 ` Robert Pluim
2020-01-20 18:00 ` Eli Zaretskii
2020-01-20 18:42 ` Robert Pluim
2020-01-27 13:26 ` mituharu
2020-01-27 18:19 ` Eli Zaretskii
2020-01-28 7:59 ` Robert Pluim
2020-01-28 8:23 ` YAMAMOTO Mitsuharu
2020-01-28 8:41 ` Robert Pluim
2020-01-28 9:02 ` Eli Zaretskii
2020-01-28 9:14 ` YAMAMOTO Mitsuharu
2020-01-28 9:42 ` Eli Zaretskii
2020-01-28 10:06 ` YAMAMOTO Mitsuharu
2020-01-28 17:37 ` Eli Zaretskii
2020-01-29 10:26 ` YAMAMOTO Mitsuharu
2020-01-29 11:09 ` Eli Zaretskii
2020-01-29 12:38 ` Eli Zaretskii
2020-01-30 9:42 ` YAMAMOTO Mitsuharu
2020-01-30 14:49 ` Eli Zaretskii
2020-01-26 17:41 ` Tomasz Kowal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsLkmXeURtMRLkfJLVU=6WQfMRKnb1+Ssg3L9kau3y-=SVqAQ@mail.gmail.com' \
--to=tomekowal@gmail.com \
--cc=39164@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).