-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] 100% reproducible emacs crash in elfeed- using emacs -q (backtrace attached) #194
Comments
this is the backtrace |
What makes it crash? Just starting Emacs? Bringing up the Elfeed search
buffer? What version of Emacs are you using and on what OS?
I don't think this bug has much to do with Elfeed (Elfeed shouldn't be
able to crash Emacs, period) but rather it's a bidi (bi-directional
text) bug in Emacs. The content of one of these feeds is tripping up
functions in bidi.c. From the backtrace, it looks like bidi_cache_find()
is returning UNKNOWN_BT, failing the assertion in bidi_find_bracket_pairs():
eassert (type == NEUTRAL_ON);
Which then causes the terminate_due_to_signal().
Something in the feed content (title, etc.) is causing Emacs to use bidi
processing, and then runs Emacs into a bad state. I wasn't able to
reproduce the crash (neither in Emacs 24.4, nor 25.1), so unfortunately
I can't narrow the problem down any further. Maybe download the feeds
with curl/wget and try viewing them within Emacs. Try running
xml-parse-region or elfeed-xml-parse-region on the buffer to see if that
crashes Emacs. You could also treat these downloads as file-protocol
feeds (e.g. "file://") to get something reproducible only from local
data.
To avoid MELPA, you can clone the Elfeed repository and run it from
there (emacs -L elfeed/ -l elfeed/elfeed.el). The idea is to narrow it
down to something small that can crash vanilla Emacs without loading any
third-party code.
I suspect it comes down to running a particular search over a particular
sequence of codepoints. Emacs has had bugs like that before.
|
thx @skeeto im updating that this is indeed an emacs bug http://lists.gnu.org/archive/html/bug-gnu-emacs/2017-01/msg00730.html which i reported and should be fixed in next emacs release thx for the help! Z |
another update! i see its elfeed-goodies which is crashing emacs not elfeed and it does indeed happen with bidi rss entries opened an issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
i have this nasty bug in elfeed (i think) that crashed emacs which i can reproduce 100% of the time. i also tried it with emacs -Q and i can reproduce it as well. im not very technical and followed a guide on how to produce a backtrace (attached in next message)
this is my minimal conf to reproduce
Would be very happy to help in trying to debugg this
best
Z
The text was updated successfully, but these errors were encountered: