From: Alan Third <alan@idiocy.org>
To: Ivan Cibrario Bertolotti <ivan.cibrario@polito.it>
Cc: 23875@debbugs.gnu.org
Subject: bug#23875: 25.0.95; Emacs crashes when closing a frame on OSX
Date: Sun, 11 Sep 2016 19:18:43 +0100 [thread overview]
Message-ID: <m2bmzu5mgs.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <2F307EFE-1F6C-462B-85C5-81877D4C88B5@polito.it> (Ivan Cibrario Bertolotti's message of "Sun, 11 Sep 2016 17:31:33 +0200")
Ivan Cibrario Bertolotti <ivan.cibrario@polito.it> writes:
> unfortunately, no. I am still using Emacs with NSTRACE_ENABLED and
> NSZombiesEnabled=YES, plus some extra debugging printouts of my own,
> related to allocation and deallocation of EmacsImages. However, I
> cannot trigger the bug anymore. In my opinion, there are two possible
> reasons for this:
>
> - triggering the bug was related to “something special” I was doing
> with Emacs at that time (somewhat unlikely), or
>
> - it is a timing-dependent bug and the debugging printouts steered
> Emacs away from it (perhaps more likely)
>
> At this time I seldom see EmacsImage allocations/deallocations in the
> Emacs trace if at all. It seems to me that most of them are allocated
> before dumping (like fringe bitmaps in bimgs, ns_draw_fringe_bitmap,
> nsterm.m) and never deallocated.
>
> I would like to force Emacs to make heavier use of EmacsImages and
> increase the probability of running into the bug again, but I don’t
> know the code base well enough for that.
>
> If you know of any way of attaining that, please let me know and I
> will give it a try.
I'm afraid I don't know any way of doing that. I guess you could just
try loading and deleting images repeatedly:
(dotimes (i 10)
(let ((image (find-image '((:type xpm :file "delete.xpm")))))
(insert (propertize " " 'display `(,image (slice .0 .0 1.0 1.0)))))
(redisplay)
(delete-backward-char 1))
That should display a bin icon ten times quickly, but I don't know if
it'll dealloc it each time or if it gets cached in some way.
Since you're the only person to report this so far I'd be inclined to
think that perhaps some part of your configuration is causing it. Would
it be possible for you to turn off the debug output and try
systematically disabling different parts of your configuration to see if
the crashes go away? That could perhaps help us narrow down what code is
causing the crash.
--
Alan Third
next prev parent reply other threads:[~2016-09-11 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 17:06 bug#23875: 25.0.95; Emacs crashes when closing a frame on OSX Ivan Cibrario Bertolotti
2016-06-30 18:50 ` Alan Third
2016-06-30 19:34 ` Ivan Cibrario Bertolotti
2016-09-11 10:15 ` Alan Third
2016-09-11 15:31 ` Ivan Cibrario Bertolotti
2016-09-11 18:18 ` Alan Third [this message]
2016-09-11 19:24 ` Ivan Cibrario Bertolotti
2016-09-12 12:58 ` Alan Third
2016-09-12 14:04 ` Ivan Cibrario Bertolotti
2016-09-12 16:52 ` Alan Third
2016-09-26 12:48 ` Ivan Cibrario Bertolotti
2016-11-11 19:14 ` Alan Third
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=m2bmzu5mgs.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=23875@debbugs.gnu.org \
--cc=ivan.cibrario@polito.it \
/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.