From: "Vladimir Alexiev" <vladimir.alexiev@ontotext.com>
To: 'Eli Zaretskii' <eliz@gnu.org>, gerd@gnu.org
Cc: 17749@debbugs.gnu.org, emacs-orgmode@gnu.org
Subject: bug#17749: 24.3.91; Crash on mwheel-scroll of org file
Date: Tue, 5 Aug 2014 11:10:16 +0300 [thread overview]
Message-ID: <27983.2907872789$1407226286@news.gmane.org> (raw)
In-Reply-To: <8361k81wha.fsf@gnu.org>
> > 1. Open emacs-crash-test.org
> > 2. Make the window smaller (e.g. 20 lines tall)
> > 2. Roll the mouse wheel down until you see the end of file, then up.
> > 3. CRASH
The specific org file doesn't matter.
The window size doesn't matter.
This crash happens to me occasionally (2-3 times a week), always on an org file, always on mwheel-up (which invokes mwheel-scroll).
Eli, can you tell something from the backtrace here?
http://lists.gnu.org/archive/html/emacs-orgmode/2014-06/txtkIBvnmHi_F.txt
The critical lines are:
die at C:\msys\home\Dani\emacs\build\src/../../emacs-24.3.91/src/alloc.c:6826
pop_it at C:\msys\home\Dani\emacs\build\src/../../emacs-24.3.91/src/xdisp.c:6060
set_iterator_to_next at C:\msys\home\Dani\emacs\build\src/../../emacs-24.3.91/src/xdisp.c:7523
move_it_in_display_line_to at C:\msys\home\Dani\emacs\build\src/../../emacs-24.3.91/src/xdisp.c:8838
> > ../../emacs-24.3.91/src/xdisp.c:6066: Emacs fatal error: assertion failed: (BUFFERP (it->object) && IT_CHARPOS (*it) == it-
> >bidi_it.charpos && IT_BYTEPOS (*it) == it->bidi_it.bytepos) || (STRINGP (it->object) && IT_STRING_CHARPOS (*it) == it-
> >bidi_it.charpos && IT_STRING_BYTEPOS (*it) == it->bidi_it.bytepos) || (CONSP (it->object) && it->method ==
> GET_FROM_STRETCH)
The code can be seen here:
https://github.com/mirrors/emacs/blob/master/src/xdisp.c#L6127
> This is an assertion violation, not a crash.
The failing assertion causes a crash, so I'm not sure what's the difference.
Is there an emacs build that doesn't crash on eassert() failure?
> Some assumption in the
> code turned out to be false, but it is not possible to know which one,
> and whether it's just a wrong assumption or a real problem.
It seems the assertion does basic consistency checks of the IT structure.
What is it->bidi_p? I don't use BIDI text: this happens on ascii org files.
I guess I'll upgrade Emacs and Org and hope for the best...
next prev parent reply other threads:[~2014-08-05 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"018001cf84c5$6252a1c0$26f7e540$@alexiev"@ontotext.com>
2014-06-10 17:54 ` bug#17749: 24.3.91; Crash on mwheel-scroll of org file Eli Zaretskii
2014-08-05 8:10 ` Vladimir Alexiev [this message]
2014-08-05 8:10 ` Vladimir Alexiev
[not found] ` <"0b2001cfb084$b11e7a50$135b6ef0$@alexiev"@ontotext.com>
2014-08-05 14:21 ` Eli Zaretskii
2015-12-26 15:26 ` Lars Ingebrigtsen
2014-06-10 16:02 Vladimir Alexiev
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='27983.2907872789$1407226286@news.gmane.org' \
--to=vladimir.alexiev@ontotext.com \
--cc=17749@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gerd@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/org-mode.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).