unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Codrut Gusoi <codrut.gusoi@gmail.com>
Cc: 26097@debbugs.gnu.org
Subject: bug#26097: Segmentation fault due to missing faces in face_cache.
Date: Mon, 20 Mar 2017 20:46:15 +0200	[thread overview]
Message-ID: <83h92nwzuw.fsf@gnu.org> (raw)
In-Reply-To: <CAJi2ve5YMc04-VUTcRRMv49jFRo3wgFyraZT4TqPHNxPQyO4sA@mail.gmail.com> (message from Codrut Gusoi on Mon, 20 Mar 2017 14:16:29 +0200)

[Please keep the bug address on the CC list.]

> From: Codrut Gusoi <codrut.gusoi@gmail.com>
> Date: Mon, 20 Mar 2017 14:16:29 +0200
> 
> I've tried watching the `used` count with `watch -l` and there is no
> place where the font cache shrinks for the current frame. I believe
> what I experineced previously was the `used` count from different
> frames (since I added a breakpoint but did not look at the frame
> address).

For the bug you describe to happen, the 'used' count of a frame's face
cache _must_ be reset to zero at some point.  There simply isn't any
other way to "lose" faces from the cache.  So if you don't see that,
it means you didn't succeed to reproduce the problem.

> Have you managed to reproduce it locally?

No.

> If not, what do you say I set up a VM in AWS and give you the IP and
> login details to take a look.

That could work if there's a more-or-less reliable recipe for
reproducing the problem.  Is there?

If there is not recipe, I won't be able to investigate the path to
disaster, and when the segfault happens, it's already too late.





  parent reply	other threads:[~2017-03-20 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 13:49 bug#26097: Segmentation fault due to missing faces in face_cache Codrut Gusoi
2017-03-14 18:20 ` Eli Zaretskii
     [not found]   ` <CAJi2ve5YMc04-VUTcRRMv49jFRo3wgFyraZT4TqPHNxPQyO4sA@mail.gmail.com>
2017-03-20 18:46     ` Eli Zaretskii [this message]
2017-03-20 19:40       ` Codrut Gusoi
2017-03-25 14:01         ` Eli Zaretskii
2017-03-25 16:46           ` Codrut Gusoi
2017-03-25 17:00             ` Eli Zaretskii

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=83h92nwzuw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26097@debbugs.gnu.org \
    --cc=codrut.gusoi@gmail.com \
    /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).