GNU bug report logs - #23368
25.0.92; xftfont.c has got a bug

Previous Next

Package: emacs;

Reported by: Masaru Nomiya <nomiya <at> galaxy.dti.ne.jp>

Date: Mon, 25 Apr 2016 07:19:02 UTC

Severity: normal

Merged with 23360, 23363

Found in version 25.0.92

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #37 received at 23368 <at> debbugs.gnu.org (full text, mbox):

From: 野宮 賢 / NOMIYA Masaru
 <nomiya <at> galaxy.dti.ne.jp>
To: handa <at> gnu.org
Cc: 23368 <at> debbugs.gnu.org, eliz <at> gnu.org
Subject: Solved! (Was: Re: bug#23368: 25.0.92; xftfont.c has got a bug)
Date: Sat, 28 May 2016 19:17:50 +0900
Hello,

In the Message; 

  Subject    : Re: bug#23368: 25.0.92; xftfont.c has got a bug
  Message-ID : <87vb2n2sug.fsf <at> gnu.org>
  Date & Time: Mon, 09 May 2016 23:45:11 +0900

handa <handa <at> gnu.org> has written:

> In article <83zis2e0ob.fsf <at> gnu.org>, Eli Zaretskii <eliz <at> gnu.org> writes:

> > Ping!

> Oops, sorry for the late response.

> > > > Date: Mon, 25 Apr 2016 15:02:40 +0900
> > > > From: Masaru Nomiya <nomiya <at> galaxy.dti.ne.jp>
> > > > 
> > > > Hello,
> > > > 
> > > > With Emacs 25.0.92, Emacs 25.0.93, and Emacs 25.1.50, Emacs start to
> > > > use 100% CPU.
> > > > That is, afetr I start Wanderlust(MUA) on Emacs, and try to open some
> > > > folders in it, Emacs starts to use 100% CPU, and unresposible.
> > > > 
> > > > I investigated the latest Emacs with git bisect.
> > > > As a result, I found that xftfont.c has got a bug as follows.
> > > 
> > > CC'ing Handa-san.  This seems to be a duplicate of bug#23360.  Can you
> > > tell which font(s) are used by Wanderlust when this happens?

> I re-read the latest xftfont_open of xftfont.c, but couldn't find a
> problem.  And, as I'm not using Wanderlust, I couldn't reproduce the
> problem.

> Could someone please find a way to reproduce the problem on GNU/Linux
> system by Emacs started with -Q.

I checked all the related files one by one. :-)
I found thst the CPU 100% usage's cause is fontconfig.
In my system, the fontconfig is 2.11.1.
I reverted this to 2.10.2's fontconfig, then problem has disappeared!

I wonder if the 2.11.1's fontconfig has got a bug?
Maybe not.

But waht's the matter, I wonder.

Thanks,

---
 Masaru Nomiya             mail-to: nomiya @ galaxy.dti.ne.jp




This bug report was last modified 9 years and 55 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.