all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Win Treese <treese@acm.org>
Cc: 34762@debbugs.gnu.org
Subject: bug#34762: Acknowledgement (26.1.92; objc[27300]: Invalid or prematurely-freed autorelease pool 0x1040021e0.)
Date: Sat, 5 Sep 2020 22:02:52 +0200 (CEST)	[thread overview]
Message-ID: <20200905200250.GC93185@breton.holly.idiocy.org> (raw)
In-Reply-To: <5E4CFA2E-BF8D-4F32-9FDA-80A004192288@acm.org>

On Thu, Sep 03, 2020 at 09:44:57PM -0400, Win Treese wrote:
> The pool seems to be pretty much irrelevant in this particular case.
> Since the menu is given to the app, and might be deallocated under
> some circumstances if it's passed back to ns_update_menu, it seems
> like simply removing the pool code is sufficient without causing a
> memory leak.

Hi Win,

Thanks for looking at this. I'm not super clear about how and why the
pools work myself, but I think you're probably right.

Can you please remove the changelog entry (the changelog files are
automatically generated now), and put it in the git commit message
instead, then use 'git format-patch' as described in CONTRIBUTE?

Have you completed the copyright paperwork?
-- 
Alan Third





  reply	other threads:[~2020-09-05 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 20:48 bug#34762: 26.1.92; objc[27300]: Invalid or prematurely-freed autorelease pool 0x1040021e0 Caroptions Caroptions
     [not found] ` <handler.34762.B.15518205747745.ack@debbugs.gnu.org>
2019-03-15 20:55   ` bug#34762: Acknowledgement (26.1.92; objc[27300]: Invalid or prematurely-freed autorelease pool 0x1040021e0.) Caroptions Caroptions
2019-03-18 12:09     ` Alan Third
2019-03-18 23:26       ` Caroptions Caroptions
2019-12-16  7:37 ` Fan Yang
2020-09-04  1:44 ` Win Treese
2020-09-05 20:02   ` Alan Third [this message]
2020-09-08 19:38     ` Win Treese
2020-09-08 20:51       ` 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=20200905200250.GC93185@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=34762@debbugs.gnu.org \
    --cc=treese@acm.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.