GNU bug report logs - #3208
23.0.93; Memory full / crash when displaying lots of characters from a large font (like Arial Unicode or Code2000) which is not explicitly selected (on Win32)

Previous Next

Full log

Message #34 received at 3208 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Jason Rumney <jasonr <at> gnu.org>
To: Kenichi Handa <handa <at> m17n.org>
Cc: 3208 <at> debbugs.gnu.org, schierlm <at> gmx.de
Subject: Re: bug#3208: 23.0.93;	Memory full / crash when displaying lots of
 characters from a	large	font (like Arial Unicode or Code2000) which is not
 explicitly	selected (on Win32)
Date: Thu, 18 Jun 2009 13:29:48 +0800

Kenichi Handa wrote:

> Anyway, font_sort_entities is called from
> font_find_for_lface (via font_select_entity).
>
> Could you please find why font_find_for_lface is called so
> releatedly by setting breakpoint in fontset_find_font (with
> condition "c == 0x2203)?
>   

I am still investigating this, but I've found that the problem is 
specific to the uniscribe font backend on Windows.  I couldn't find the 
root cause by debugging, so I am now trying profiling to narrow the search.

With uniscribe font backend enabled, font_load_for_lface gets called 
124k times from 165k calls to fontset_find_font before the memory 
overflow. The glyph that gets displayed is a double-width katakana YO 
from MS Mincho font (it seems the font defines the same glyph to be used 
for mathematical THERE EXISTS).

With only the gdi font backend enabled, font_load_for_lface gets called 
only once from 399k calls to fontset_find_font, but the default Courier 
New font is used to display the characters even though it does not 
contain a glyph (so the default empty box glyph is displayed).

Previous Next

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