From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: bug#1748: 23.0.60; display of multiple frames: refresh and memory problems
Date: Tue, 30 Dec 2008 22:03:03 -0800 [thread overview]
Message-ID: <006401c96b0d$7223b760$0200a8c0@us.oracle.com> (raw)
I see this with my own setup, which uses more faces etc., but I
can reproduce it to some extent in emacs -Q. When many frames
are open, I see these problems, in order of severity, severity
worsening with more frames:
1. Redisplay problems. If a frame is partly behind another frame or
other window-mgr window, and the occluding frame is iconified or moved
out of the way, then the formerly hidden part of the occluded frame
that is now visible is not refreshed - it stays blanked out.
With enough frames it is never refreshed until I do `C-l'. The result
is that in practice, with my setup, having several frames means I must
often do `C-l' to see a frame.
2. Memory problems. With enough frames opened, I get a memory warning
from Emacs, or Emacs hangs altogether, or it crashes.
With my own setup, the redisplay problems happen with even a few frames,
the memory 75% warning appears with about 15 frames. And if I open, say 20
frames, Emacs hangs and I need to use the task manager to kill it - or it
crashes. With Emacs 20 through 22, I never see any such problems. I can have
several Emacses open at once, with any number of frames for each. As soon as I
use Emacs 23, I run into these problems.
With emacs -Q, it takes many, many more frames for problem #1 to appear, and I
have not yet seen problem #2. As I write this, I'm seeing the redisplay problem
somewhat in emacs -Q, with 30 frames open. But the problem is still slight in
emacs -Q: if I move a frame the others are redisplayed pretty quickly.
If I can isolate anything else in my own setup that contributes to this I'll
send it along, but that might not be soon or easy.
A quick way to test the redisplay problem with emacs -Q is to load dired-x.el,
set pop-up-frames to t, and eval this:
(defun dired-simultaneous-find-file (file-list option)
"Same as original, but respects `pop-up-frames'."
(let (size)
(cond ((and option (natnump option))
(while file-list (find-file-noselect (car file-list)) (pop
file-list)))
((or pop-up-frames option)
(while file-list (find-file-other-frame (car file-list)) (pop
file-list)))
(t
(setq size (/ (window-height) (length file-list)))
(when (> window-min-height size)
(error "Too many files to visit simultaneously. Try C-u prefix."))
(find-file (car file-list))
(pop file-list)
(while file-list
;; Vertically split off a window of desired size.
;; Upper window will have SIZE lines.
;; Select lower (larger) window. We split it again.
(select-window (split-window nil size))
(find-file (car file-list))
(pop file-list))))))
Then mark lots of files in Dired and hit `F' to open them all in
separate frames.
In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
of 2008-12-30 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
next prev reply other threads:[~2008-12-31 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49BD160A.6080106@gnu.org>
2008-09-09 16:51 ` bug#950: CVS Emacs on Windows XP fails to draw contents of new frame Francis Litterio
2008-09-11 8:54 ` martin rudalics
2008-09-11 12:15 ` Juanma Barranquero
[not found] ` <mailman.18995.1221124075.18990.bug-gnu-emacs@gnu.org>
2008-09-11 14:34 ` Francis Litterio
2009-03-15 15:00 ` bug#950: marked as done (CVS Emacs on Windows XP fails to draw contents of new frame) Emacs bug Tracking System
2008-12-31 6:03 ` Drew Adams [this message]
2009-03-15 15:00 ` bug#1748: marked as done (23.0.60; display of multiple frames: refresh and memory problems) Emacs bug Tracking System
2009-03-01 20:51 ` bug#2524: 23.0.91; Frame beneath the current one not fully redisplayed on w32 Eli Zaretskii
2009-03-01 21:50 ` Drew Adams
2009-03-02 8:47 ` Juanma Barranquero
2009-03-15 15:00 ` bug#2524: marked as done (23.0.91; Frame beneath the current one not fully redisplayed on w32) Emacs bug Tracking System
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006401c96b0d$7223b760$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=1748@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).