From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.ciao.gmane.org!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.bugs Subject: bug#34138: 27.0.50; Delayed display of PDF file images Date: Mon, 21 Jan 2019 19:17:53 +0100 Message-ID: <87womxdgdq.fsf@gmx.net> References: <871s58e4gh.fsf@gmx.net> <5C443CB1.3050208@gmx.at> <87h8e3h90z.fsf@gmx.net> <5C4483B7.1060604@gmx.at> <87d0orgz0a.fsf@gmx.net> <837eezbazk.fsf@gnu.org> <878szfgwdu.fsf@gmx.net> <8336pnb9cq.fsf@gnu.org> <874la3gujy.fsf@gmx.net> <831s57b7ev.fsf@gnu.org> <87zhrvfdzu.fsf@gmx.net> <83zhrv9qe5.fsf@gnu.org> <87sgxnf48d.fsf@gmx.net> <83pnsq9f47.fsf@gnu.org> <871s56dm5q.fsf@gmx.net> <83lg3e9dd6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.org; posting-host="ciao.gmane.org:195.159.176.228"; logging-data="132877"; mail-complaints-to="usenet@ciao.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 34138@debbugs.gnu.org, politza@hochschule-trier.de, tsdh@gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jan 21 19:53:56 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glehf-000Xw1-53 for geb-bug-gnu-emacs@m.gmane.org; Mon, 21 Jan 2019 19:53:47 +0100 Original-Received: from localhost ([127.0.0.1]:57916 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gleYe-0003I6-Ll for geb-bug-gnu-emacs@m.gmane.org; Mon, 21 Jan 2019 13:44:28 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gleA3-0006Nd-Hb for bug-gnu-emacs@gnu.org; Mon, 21 Jan 2019 13:19:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gleA2-0006Iy-Oy for bug-gnu-emacs@gnu.org; Mon, 21 Jan 2019 13:19:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41140) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gleA2-0006Ik-LV for bug-gnu-emacs@gnu.org; Mon, 21 Jan 2019 13:19:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gleA2-0004JL-Ce for bug-gnu-emacs@gnu.org; Mon, 21 Jan 2019 13:19:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Stephen Berman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 21 Jan 2019 18:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34138 X-GNU-PR-Package: emacs Original-Received: via spool by 34138-submit@debbugs.gnu.org id=B34138.154809468616491 (code B ref 34138); Mon, 21 Jan 2019 18:19:02 +0000 Original-Received: (at 34138) by debbugs.gnu.org; 21 Jan 2019 18:18:06 +0000 Original-Received: from localhost ([127.0.0.1]:40417 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gle98-0004Hv-71 for submit@debbugs.gnu.org; Mon, 21 Jan 2019 13:18:06 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:60949) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gle95-0004HR-M1 for 34138@debbugs.gnu.org; Mon, 21 Jan 2019 13:18:04 -0500 Original-Received: from rosalinde ([178.1.151.238]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lqn7e-1hOqm10drW-00eOfR; Mon, 21 Jan 2019 19:17:55 +0100 In-Reply-To: <83lg3e9dd6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Jan 2019 18:36:37 +0200") X-Provags-ID: V03:K1:N/W3HSaTp36MdwbN7jdgrzl6dpEX1MMZqsshkJ3NS83qCMlHCZP axTqcdtklxHmjBxO/GZoMZHCo+XtIMirkA0YYOK84JhUywv/sMK5Vq4SC2a3Lv1NWkCt8FH KRrBet4S9t7ZIrojJ7wDto6lKJJN5OV7STeXUG+Mcd9JJCktANwigVlcVXPAC1AInvIal/p jdQq0ixNT+P4draWYYHKQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:HV5EFwef/fk=:a/20Xk3DK6p6yOUeEMFop3 e5ifnCzM9SYXwBR6FuPiqq3YbYtP5po8/YjBJje1ObVIQ3nvncY7AMPz5FcpTYySBcO+C+k4m L5HfUlB+t8smlyPXw8BoXG8r4zAMN18zF9doblWBZMA3tChGxOzgMJhkKkEIMCdEc3dsz4kfy MVsj9RnI9aUGgNzEG7wVU++wstkXaZClIRPiwcZdZfqedZPx5HWVcw7J5JsoZ8Wo20fIseZU3 EyhwjgvJ3biLvL6lyQnbFsMyEGah8D2Q+tNVS8woagh1vb+NtQe2idpgyf4i3AM15+6Iros2q Ytpavb5SaO5z9ZnJ2+x8Wc0e7dKvDL4+nZ3k/KaGUSyx2fJL25+YBzP/x8d7Xu8o7T5bZgewT C1t/fcyzAsg1UCAfHP3uQl61rU1S4hovtGzvP1C/gcrZdnOzdIvBybXalm9UGJcQfT0RlK/s9 jRQLIGmcSdmO4hq95iNEuu9m1rI+P+rL8ccqLrc7DolOjePkyYsTPwK+kgZpIM8hNLQMiRpsy lCNTSHs0G0tGnZ3Doyhvf68tbvOjIofWaMym4nzMD+4JFZptrTjofXy3SUlv+51XlQQ2ySRXy Kn9tq1Zp1H0HNoXQsKQ02e272926Rmh85xXBCU/Sxn1NeczQ4MyvXmIGwfD86fbdl1N+OwXVd q4QejC8F+MNREnKgPiIcE18nytpNWc7TfEUr2xHm8tXlPDWTauSzVHGfPo2fP8gQsTI3KuvlX vUY80Xd1/IM4f5+EFpVSSdQ3PbkfjvniyaU+3U1z8sA7Ou79aXE1Fsv0T7QKeH/GpSXyh8M5 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:154651 Archived-At: On Mon, 21 Jan 2019 18:36:37 +0200 Eli Zaretskii wrote: >> From: Stephen Berman >> Cc: rudalics@gmx.at, 34138@debbugs.gnu.org, politza@hochschule-trier.de, >> tsdh@gnu.org >> Date: Mon, 21 Jan 2019 17:13:05 +0100 >> >> > Still weird: this says that Emacs simply waits for any input to >> > arrive, a.k.a. "is idle". >> > >> > You've mentioned before that one of the two scenarios where you see >> > this problem produces a much longer delay -- could you repeat the same >> > procedure during that long delay, and show the backtrace from that >> > session? Maybe we will see something more interesting there. >> >> This (and all the other backtraces I posted or mentioned) was from the >> scenario where I see the long delay, i.e. using pdf-view-mode > > So does it mean that during this time Emacs waits for the external > process (is it Ghostscript? ImageMagick?) to complete? That's all I > see in the backtrace. Not Ghostscript but the PDF rendering library Poppler; I think ImageMagick can be used for some functionality, but it's not required. But Andreas Politza can surely answer this best and provide more details. > Can you establish (e.g., by adding 'message' lines to the Lisp source) > where in the pdf-view-mode's sources this delay starts? IOW, what is > the last thing pdf-view-mode does before the delay begins? I don't know where it makes sense to output messages. I did step through pdf-view-mode and the last function it calls, pdf-view-goto-page, but when that function returns it's just the raw PDF that's displayed. I then instrumented all pdf-view defuns and while stepping though, the PDF image appeared on calling pdf-view-maybe-redisplay-resized-windows, which is added to window-configuration-change-hook in pdf-view-mode. So it appears that the delay starts between pdf-view-goto-page returning and pdf-view-maybe-redisplay-resized-windows being called, but when stepping through the long call chain, I did not see the transition (no raw PDF was displayed, just the rendered image at the end). Steve Berman