From: Ivan Cibrario Bertolotti <ivan.cibrario@polito.it>
To: Alan Third <alan@idiocy.org>
Cc: 23875@debbugs.gnu.org
Subject: bug#23875: 25.0.95; Emacs crashes when closing a frame on OSX
Date: Sun, 11 Sep 2016 17:31:33 +0200 [thread overview]
Message-ID: <2F307EFE-1F6C-462B-85C5-81877D4C88B5@polito.it> (raw)
In-Reply-To: <m2eg4q68uk.fsf@breton.holly.idiocy.org>
Hi Alan,
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.
Thanks,
Ivan
> On 11 Sep 2016, at 12:15, Alan Third <alan@idiocy.org> wrote:
>
> Ivan Cibrario Bertolotti <ivan.cibrario@polito.it> writes:
>
>>> I'm not sure how to go about debugging this stuff, but NSZombiesEnabled
>>> seems to be the way:
>>>
>>> $ NSZombiesEnabled=YES /path/to/emacs.app/Contents/MacOS/Emacs
>>>
>>> this should print out a message when an object is deallocated too many
>>> times, instead of just crashing.
>>
>>> --
>>> Alan Third
>>
>> I understand, it looks nasty indeed and it happens on average only
>> once a day. Thank you for the hint. I will keep using Emacs with
>> NSTRACE_ENABLED and NSZombiesEnabled=YES. Will get back as soon as I
>> have more substantial information.
>
> Hi Ivan, did you ever get anywhere with this?
> --
> Alan Third
next prev parent reply other threads:[~2016-09-11 15:31 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 [this message]
2016-09-11 18:18 ` Alan Third
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=2F307EFE-1F6C-462B-85C5-81877D4C88B5@polito.it \
--to=ivan.cibrario@polito.it \
--cc=23875@debbugs.gnu.org \
--cc=alan@idiocy.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.