all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 14981@debbugs.gnu.org, chad <yandros@MIT.EDU>
Subject: bug#14981: 24.3.50; NS port error when closing maximized frames
Date: Sat, 11 Jun 2016 15:42:57 +0100	[thread overview]
Message-ID: <m2bn37zszy.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <FE06628D-0C06-4F40-B3CA-11927E013676@swipnet.se> ("Jan \=\?utf-8\?Q\?Dj\=C3\=A4rv\=22's\?\= message of "Tue, 30 Jul 2013 11:31:30 +0200")

Jan Djärv <jan.h.d@swipnet.se> writes:

> 29 jul 2013 kl. 17:53 skrev chad <yandros@MIT.EDU>:
>
>> Using the latest bzr head, if I open a new frame (C-x 5 C-f), then
>> fullscreen the new frame (F11), then close that new frame while it's
>> still maximized (C-x 5 0), I get this message to stderr:
>> 
>> 	2013-07-29 10:46:15.559 Emacs[83142:303] void _NSMoveWindowToSpaceUnlessSticky(NSInteger, CGSSpaceID): CGSGetWindowTags(cid, win, tags, kCGSRealMaximumTagSize) returned CGError 1000 on line 1247 
>> 
>> This seems to be repeatable with emacs -Q.
>> 
>
> I don't know how to fix this, it seems to be a bug in OSX. It is not
> fatal, but each error leaks some memory, which is bad.

I don't get this error in Emacs 25 under El Capitan. Perhaps it's been
fixed. Can anyone confirm whether they still see it?
-- 
Alan Third





  reply	other threads:[~2016-06-11 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 15:53 bug#14981: 24.3.50; NS port error when closing maximized frames chad
2013-07-30  9:31 ` Jan Djärv
2016-06-11 14:42   ` Alan Third [this message]
2016-06-12  0:23     ` Chad Brown
2016-06-27 20:54       ` Alan Third
  -- strict thread matches above, loose matches on Subject: below --
2016-06-14  8:24 Chad Brown

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=m2bn37zszy.fsf@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=14981@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=yandros@MIT.EDU \
    /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.