all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 9904@debbugs.gnu.org, bojohan@gnu.org
Subject: bug#9904: 24.0.90; Crash in show_mouse_face
Date: Sat, 29 Oct 2011 17:33:51 +0200	[thread overview]
Message-ID: <83ty6r95i8.fsf@gnu.org> (raw)
In-Reply-To: <87pqhfdedq.fsf@gnu.org>

> From: Chong Yidong <cyd@gnu.org>
> Cc: Johan Bockgård <bojohan@gnu.org>,  9904@debbugs.gnu.org
> Date: Sat, 29 Oct 2011 23:08:33 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Emacs segfaulted in show_mouse_face last week (revno 106154, I
> >> think). I have a core file.
> >
> > FWIW, I cannot find any change during the last 2 weeks that could
> > somehow be related.
> >
> > Where could this garbled "window" come from? some GC or
> > memory-allocation snafu?
> 
> Might the window assigned to dpyinfo->mouse_highlight->hlinfo have
> gotten garbage collected?  Does the GC mark that slot?  I can't find the
> place where it does so.

If the window was garbage collected, it was deleted first, right?  My
testing indicates that deleting a window calls clear_mouse_face
indirectly (because deleting a window from a frame runs
frame_up_to_date_hook for that frame, where we call
note_mouse_highlight.  So this ought to work OK, I think.

Maybe we should invalidate mouse_face_window inside
delete-window-internal, to make sure this window is no longer
referenced in dpyinfo->mouse_highlight->hlinfo?






  reply	other threads:[~2011-10-29 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 13:44 bug#9904: 24.0.90; Crash in show_mouse_face Johan Bockgård
2011-10-29 14:09 ` Eli Zaretskii
2011-10-29 15:08   ` Chong Yidong
2011-10-29 15:33     ` Eli Zaretskii [this message]
2012-02-12  4:31       ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ty6r95i8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9904@debbugs.gnu.org \
    --cc=bojohan@gnu.org \
    --cc=cyd@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.