comparison admin/FOR-RELEASE @ 61602:71c8a6678c21

*** empty log message ***

61601:aaa0bead8bc5

Redisplay may loop if there is an error in some display property, e.g.
     (space 'left-margin)

A fix would be to somehow disable handling of display properties if an error
is encountered.


** custom mode-line face makes Emacs freeze up

From: Stephen Berman <[e-mail]>
Date: Sun, 24 Oct 2004 02:08:56 +0200

1. Start Emacs with -q -no-site-file.

2. Type `M-x customize-face' and at the prompt `mode-line'.

3. In the Custom buffer for mode-line face
   a. check width and give it the value `narrow';
   b. check height and give it the value 120 in 1/10 pt;
   c. check underline and give it the value `on' (or `colored');
   d. check overline and give it the value `on' (or `colored').

4. Set for current session.

5. Invoke Ediff on any two files.

6. Now Emacs is frozen and consumes 95-99% of CPU.

The customizations in step 3 appear to be the minimum necessary to
induce this bug.  Leave out any one of them and Ediff runs without a
problem.  Also if the 1/10 point value of height is 130 or greater
there's no bug (with the default font family; with e.g. Helvetica the
bug is induced only by a value of 100 or less).

I've noticed this freeze up only when invoking Ediff.  The only thing
I've been able to do is kill Emacs externally, via top or with kill
when run in gdb, after interrupting.  When the freeze up happens
within a gdb session, there is no automatic debugging feedback.  After
interrupting I can get a backtrace, here's an example:

Update: Maybe only reveals itself when compiled with GTK+


* DOCUMENTATION

** Document Custom Themes.

61602:71c8a6678c21

Redisplay may loop if there is an error in some display property, e.g.
     (space 'left-margin)

A fix would be to somehow disable handling of display properties if an error
is encountered.


* DOCUMENTATION

** Document Custom Themes.