unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-pretest-bug@gnu.org, 3422@emacsbugs.donarmstrong.com
Subject: bug#3422: 23.0.94; window-height returns window buffer
Date: Sat, 30 May 2009 16:07:03 +0200	[thread overview]
Message-ID: <e01d8a50905300707u5a36452bu4fff9e243918b3fa@mail.gmail.com> (raw)
In-Reply-To: <4A213BB7.3010608@gnu.org>

On Sat, May 30, 2009 at 3:59 PM, Jason Rumney <jasonr@gnu.org> wrote:
> Lennart Borgman wrote:
>>
>> I do not think I can reproduce this, but (window-height win) just
>> returned the buffer win was displaying. I can reproduce it now, but I
>> doubt I can when I have restarted Emacs.
>>
>
> Are you saying that memory is corrupted such that the current window's
> total_lines member holds a buffer?
>
>> This was with my patched Emacs, but there is no patches in window.c.
>
> It doesn't matter where your patches are if they are causing the memory
> corruption.
>
>>  I
>> suspect that this has something to do with frame creation since I have
>> seen many crashes there. Another possibility is w32 resources. I see a
>> steady increase in GDI Objects in Windows Task Manager and when that
>> starts to get high very strange things can happen (though it is
>> perhaps some other resource that is depleted).
>>
>
> What are you doing when you see this steady increase? Do you also see it in
> the current pretest or CVS trunk?

I do not think this is related to Emacs. It is a bug in xp (and I
think w2k too) in the handling of sticky keys. At each menu invocation
and window switching xp eats gdi objects. I have actually reported
this to ms, but ...





      reply	other threads:[~2009-05-30 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 13:20 bug#3422: 23.0.94; window-height returns window buffer Lennart Borgman
2009-05-30 13:47 ` Eli Zaretskii
2009-05-30 13:55   ` Lennart Borgman
2011-07-10  0:26   ` Glenn Morris
2011-07-10  0:42     ` Lennart Borgman
2009-05-30 13:59 ` Jason Rumney
2009-05-30 14:07   ` Lennart Borgman [this message]

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=e01d8a50905300707u5a36452bu4fff9e243918b3fa@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=3422@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=jasonr@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).