From: Eli Zaretskii <eliz@gnu.org>
To: vladimir.alexiev@ontotext.com
Cc: 17749@debbugs.gnu.org, emacs-orgmode@gnu.org
Subject: Re: bug#17749: 24.3.91; Crash on mwheel-scroll of org file
Date: Tue, 05 Aug 2014 17:21:12 +0300 [thread overview]
Message-ID: <83r40vow4n.fsf@gnu.org> (raw)
In-Reply-To: <"0b2001cfb084$b11e7a50$135b6ef0$@alexiev"@ontotext.com>
> From: "Vladimir Alexiev" <vladimir.alexiev@ontotext.com>
> Cc: <17749@debbugs.gnu.org>,
> <emacs-orgmode@gnu.org>
> Date: Tue, 5 Aug 2014 11:10:16 +0300
>
> > > 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
No, sorry. I really need to reproduce this on my machine and run
Emacs under a debugger to see what happens and why.
Please try to come up with a recipe starting from "emacs -Q". It is
OK to include customizations and loading of optional packages, but
please try to find the minimal set of those, as too many of them
complicate debugging.
> > 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?
If Emacs is configured without --enable-checking (which is what
happens in released versions), all the eassert lines compile to
nothing.
> > 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.
Yes. But without details, I cannot know what caused it or how to fix
it.
> What is it->bidi_p? I don't use BIDI text: this happens on ascii org files.
The display engine always works in bidirectional mode, this has been
so since Emacs 24.1.
next prev parent reply other threads:[~2014-08-05 14:21 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
2014-08-05 8:10 ` Vladimir Alexiev
[not found] ` <"0b2001cfb084$b11e7a50$135b6ef0$@alexiev"@ontotext.com>
2014-08-05 14:21 ` Eli Zaretskii [this message]
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=83r40vow4n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17749@debbugs.gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=vladimir.alexiev@ontotext.com \
/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).