From: Chad Brown <yandros@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 14981@debbugs.gnu.org, "chad brown" <yandros@MIT.EDU>,
"Jan Djärv" <jan.h.d@swipnet.se>
Subject: bug#14981: 24.3.50; NS port error when closing maximized frames
Date: Sat, 11 Jun 2016 17:23:51 -0700 [thread overview]
Message-ID: <4298000D-64F8-4750-99FD-090E5B8AAFEC@gmail.com> (raw)
In-Reply-To: <m2bn37zszy.fsf@breton.holly.idiocy.org>
> On 11 Jun 2016, at 07:42, Alan Third <alan@idiocy.org> wrote:
>
> 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?
I also do NOT see this with emacs-25 HEAD on mac os x 10.11.5. Maybe poke emacs-devel and see if anyone can try it on an older release?
Thanks,
~Chad
next prev parent reply other threads:[~2016-06-12 0:23 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
2016-06-12 0:23 ` Chad Brown [this message]
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=4298000D-64F8-4750-99FD-090E5B8AAFEC@gmail.com \
--to=yandros@gmail.com \
--cc=14981@debbugs.gnu.org \
--cc=alan@idiocy.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.