all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 24109@debbugs.gnu.org, djcb@djcbsoftware.nl,
	Christophe.Troestler@umons.ac.be
Subject: bug#24109: 24.5; Long lines in message mode make Emacs irresponsive
Date: Tue, 30 Aug 2016 18:29:07 +0300	[thread overview]
Message-ID: <838tvenum4.fsf@gnu.org> (raw)
In-Reply-To: <20160830123848.qxgg3hcawx4yqw4j@eab16011nb> (message from Yuri D'Elia on Tue, 30 Aug 2016 14:38:48 +0200)

> Date: Tue, 30 Aug 2016 14:38:48 +0200
> From: Yuri D'Elia <wavexx@thregr.org>
> 
> I've also stumbled on this bug when using mu4e.
> I've rebuilt the current emacs from git (4961cc3f368d9114c305efe6243987bcfa3fd29b) with:
> 
>   '--with-x-toolkit=lucid' 'CFLAGS=-O0 -ggdb3'
> 
> I've used lucid as that's the normal tk I use. I managed to hang emacs the same
> way I currently do on 24.5 (from debian), by scrolling through a *mu4e-headers*
> view. C-g does nothing.
> 
> The backtrace is as follows:
> [...]

I see nothing abnormal in the backtrace, at least not at a glance.

> Emacs is stuck in try_window calling display_line, where the "it" parameter remains constant.

What do you mean by "it parameter remains constant"?  That is a large
structure; what parts of it remain constant?

> I'm attaching the output of *it in the email, hoping it might be useful.

Thanks, but it by itself doesn't help enough.  I need to see the text
that Emacs is trying to display, at least.





  parent reply	other threads:[~2016-08-30 15:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 11:36 bug#24109: 24.5; Long lines in message mode make Emacs irresponsive Christophe Troestler
2016-07-30  7:07 ` Eli Zaretskii
2016-07-30 12:38   ` Christophe Troestler
2016-07-30 14:52     ` Clément Pit--Claudel
2016-07-30 15:55     ` Eli Zaretskii
2016-07-30 17:01       ` martin rudalics
2016-07-30 17:13         ` Eli Zaretskii
2016-07-30 17:30           ` martin rudalics
2016-07-30 18:02             ` Eli Zaretskii
2016-07-30 18:30               ` John Mastro
2016-07-30 18:48                 ` Eli Zaretskii
2016-07-30 19:22                 ` Dirk-Jan C. Binnema
2016-08-30 12:38 ` Yuri D'Elia
2016-08-30 12:45   ` Yuri D'Elia
2016-08-30 15:29   ` Eli Zaretskii [this message]
2016-08-30 15:51     ` Yuri D'Elia
2016-08-30 16:25       ` Eli Zaretskii
2016-08-31  9:15         ` Yuri D'Elia
2016-08-31 14:37           ` Eli Zaretskii
2016-08-31 15:51             ` Yuri D'Elia
2016-08-31 16:12               ` Eli Zaretskii
2016-08-31 16:49                 ` Yuri D'Elia
2016-09-01  2:35                   ` Eli Zaretskii
2016-09-01 14:30                     ` Eli Zaretskii
2016-09-01 14:39                       ` Yuri D'Elia
2016-09-01 14:48                         ` Yuri D'Elia
2016-09-01 15:18                           ` Eli Zaretskii
2016-09-01 15:37                             ` Yuri D'Elia
2016-09-01 16:00                               ` Eli Zaretskii
2016-09-03 13:25                                 ` Eli Zaretskii
     [not found]                       ` <28e7ddc58bcfeec0@fake-msgid>
2016-10-01 17:10                         ` Yuri D'Elia
2016-10-01 17:47                           ` Eli Zaretskii
2016-10-01 18:25                           ` Yuri D'Elia
2016-10-02  7:09                             ` Eli Zaretskii
2016-10-04  7:16                               ` Yuri D'Elia
2016-10-04  7:56                                 ` Eli Zaretskii
2016-10-08  7:55                               ` Eli Zaretskii
2016-10-08 15:27                                 ` Yuri D'Elia
2016-10-08 15:38                                   ` Eli Zaretskii
2016-10-08 15:42                                     ` Yuri D'Elia
2016-10-09 19:21                                   ` Christophe Troestler
2016-10-10  6:08                                     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838tvenum4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24109@debbugs.gnu.org \
    --cc=Christophe.Troestler@umons.ac.be \
    --cc=djcb@djcbsoftware.nl \
    --cc=wavexx@thregr.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.