From: Stefan Kangas <stefan@marxist.se>
To: Mike Dupont <jamesmikedupont@googlemail.com>
Cc: 27446@debbugs.gnu.org
Subject: bug#27446: 25.1; Crashing on rendering of Font
Date: Mon, 04 Nov 2019 10:27:11 +0100 [thread overview]
Message-ID: <87imo0c7ps.fsf@marxist.se> (raw)
In-Reply-To: <CAF0qKV094kcH_gksdBJ3Eb0F3VPRQ+aKAMe+4W+nY3k+T7CtHA@mail.gmail.com> (Mike Dupont's message of "Tue, 27 Jun 2017 20:16:34 -0400")
Mike Dupont <jamesmikedupont@googlemail.com> writes:
> see core file. Anyway, If this is not a problem then it is not a
> problem. I am using the debian versions mentioned, can you try them?
I tried displaying the below file on current master and Emacs 26.1 but
didn't see any crashes. Are you still seeing this on Emacs 26 or
later?
If I don't hear back from you within a couple of weeks, I'll just
assume that this has been fixed and close this bug report.
Best regards,
Stefan Kangas
> On Tue, Jun 27, 2017 at 10:57 AM, handa <handa@gnu.org> wrote:
>> In article <CAF0qKV2qz_sckpk7-12uq5X1_0MsRfUS3yU9BFnRJ49wEawE_Q@mail.gmail.com>, Mike Dupont <jamesmikedupont@googlemail.com> writes:
>>
>>> I made the file and the core available
>>> https://gist.github.com/h4ck3rm1k3/ad5d3d9927883c15a07d1b394c99d332
>>
>> Thank you. I tried to display all portions of the above file, but
>> Emasc did not crash.
>>
>> ---
>> K. Handa
>> handa@gnu.org
>>
>>
>>> On Sat, Jun 24, 2017 at 2:30 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>>> From: handa <handa@gnu.org>
>>>>> Cc: Eli Zaretskii <eliz@gnu.org>, 27446@debbugs.gnu.org
>>>>> Date: Sat, 24 Jun 2017 13:03:25 +0900
>>>>>
>>>>> In article <83bmpfum7h.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>>>>> [...]
>>>>> > > It shows line 2306, I was scrolling down.
>>>>>
>>>>> > Thanks. CC'ing Handa-san, in the hope that he could look into this
>>>>> > issue.
>>>>>
>>>>> The file has hebrew, devanagari, gothic, Armenian charactes at around
>>>>> the line 2306. But, I can't reproduce the crash. Perhaps we are using
>>>>> different fonts.
>>> >
>>> > One problem might be that the results of the query on that page change
>>> > all the time. So perhaps the file you were using is different from
>>> > what Mike tried. Mike, does this happen with any query you run, or
>>> > just with the one you did back when you reported the crash? If the
>>> > latter, can you make the file available somewhere?
>>> >
>>> > Thanks.
>>
>>
>>
>>> --
>>> James Michael DuPont
>>
next prev parent reply other threads:[~2019-11-04 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 11:38 bug#27446: 25.1; Crashing on rendering of Font Mike Dupont
2017-06-22 12:14 ` bug#27446: attachments Mike Dupont
2017-06-22 15:08 ` bug#27446: 25.1; Crashing on rendering of Font Eli Zaretskii
2017-06-23 0:23 ` Mike Dupont
2017-06-23 8:45 ` Eli Zaretskii
2017-06-24 4:03 ` handa
2017-06-24 6:30 ` Eli Zaretskii
2017-06-24 17:32 ` Mike Dupont
2017-06-27 14:57 ` handa
2017-06-28 0:16 ` Mike Dupont
2019-11-04 9:27 ` Stefan Kangas [this message]
2019-12-05 11:13 ` Stefan Kangas
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=87imo0c7ps.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=27446@debbugs.gnu.org \
--cc=jamesmikedupont@googlemail.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 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.