[debbugs-tracker] bug#15870: closed (24.3.50; frameset: Restoration and drawing issues)

[GNU bug Tracking System]

Your message dated Tue, 01 Jan 2002 05:53:03 +0530
with message-id <address@hidden>
and subject line Re: bug#15870: 24.3.50; frameset: Restoration and drawing 
issues
has caused the debbugs.gnu.org bug report #15870,
regarding 24.3.50; frameset: Restoration and drawing issues
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
15870: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15870
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: 24.3.50; frameset: Restoration and drawing issues Date: Tue, 12 Nov 2013 14:06:40 +0530

Basic configuration:

    (custom-set-variables
     '(desktop-base-file-name "~/.emacs.desktop")
     '(desktop-save-mode t))

The basic steps:  
http://lists.gnu.org/archive/html/emacs-devel/2013-11/msg00330.html

Tips for reproducing this bug,

1. Have "large amount" of buffers open - I have around 20 c buffers open
   from ~/src/emacs/trunk/src/

2. Have your .emacs impose some amount of load.  For example, load few
   .el files or add some big chunk of customizations.

ps: Don't ask for a precise recipe.  

----------------------------------------------------------------

See the attached screenshot - There are 3 png files in the attached .zip
file.

Step-1: 0s
Step-2: Appears around 4.2 sec
Step-3: Appears around 8.0s

frameset.zip
Description: Zip archive

In GNU Emacs 24.3.50.5 (i686-pc-linux-gnu, GTK+ Version 2.20.1)
 of 2013-11-12 on debian-6.05
Bzr revision: 115070 address@hidden
Windowing system distributor `The X.Org Foundation', version 11.0.10707000
System Description:     Debian GNU/Linux 6.0.5 (squeeze)

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#15870: 24.3.50; frameset: Restoration and drawing issues
>
>
>
>
> Date: 
>
> Tue, 01 Jan 2002 05:53:03 +0530
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
>
>
>
>
> OP here.  Not a bug.
>
>
> --- End Message ---