[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#23856: closed (25.0.95; Crash on cancel print dial

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#23856: closed (25.0.95; Crash on cancel print dialogue)
Date: Sun, 17 Jul 2016 21:21:01 +0000

Your message dated Sun, 17 Jul 2016 22:20:40 +0100
with message-id <address@hidden>
and subject line Re: bug#23856: [PATCH] Remove separate pool for popup dialogs 
has caused the debbugs.gnu.org bug report #23856,
regarding 25.0.95; Crash on cancel print dialogue
to be marked as done.

(If you believe you have received this mail in error, please contact

23856: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23856
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.95; Crash on cancel print dialogue Date: Mon, 27 Jun 2016 21:05:11 +0200
Occasionally I press cmd-p by mistake. When I press cancel in the print 
dialogue, emacs crashes. This is annoying. Let me know if there is anything I 
can do to help locate the root cause.

1. Press Cmd-P
2. Press Esc

In GNU Emacs (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 
10.9.5 (Build 13F1603))
of 2016-06-11 built on builder10-9.local
Windowing system distributor 'Apple', version 10.3.1404
Configured using:
'configure --with-ns '--enable-locallisppath=/Library/Application

Configured features:

Important settings:
  value of $LC_ALL: en_US.UTF-8
  value of $LC_CTYPE: UTF-8
  value of $LANG: en_NO.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
C-x C-g is undefined
user-error: The mark is not set now, so there is no region
user-error: No mark set in this buffer
Print buffer *scratch*? y
Making completion list... [3 times]

Load-path shadows:
None found.

(shadow sort mail-extr lpr emacsbug message dired format-spec rfc822 mml
mml-sec password-cache epg epg-config gnus-util mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail
rfc2047 rfc2045 ietf-drums mm-util help-fns help-mode easymenu
cl-loaddefs pcase cl-lib mail-prsvr mail-utils time-date mule-util
tooltip eldoc electric uniquify ediff-hook vc-hooks lisp-float-type
mwheel ns-win ucs-normalize term/common-win tool-bar dnd fontset image
regexp-opt fringe tabulated-list newcomment elisp-mode lisp-mode
prog-mode register page menu-bar rfn-eshadow timer select scroll-bar
mouse jit-lock font-lock syntax facemenu font-core frame cl-generic cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese charscript case-table epa-hook
jka-cmpr-hook help simple abbrev minibuffer cl-preloaded nadvice
loaddefs button faces cus-face macroexp files text-properties overlay
sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote kqueue cocoa ns multi-tty
make-network-process emacs)

Memory information:
((conses 16 196218 11101)
(symbols 48 19494 0)
(miscs 40 49 299)
(strings 32 15007 6042)
(string-bytes 1 433033)
(vectors 16 32859)
(vector-slots 8 648289 6769)
(floats 8 158 143)
(intervals 56 218 10)
(buffers 976 13))

--- End Message ---
--- Begin Message --- Subject: Re: bug#23856: [PATCH] Remove separate pool for popup dialogs (bug#23856) Date: Sun, 17 Jul 2016 22:20:40 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (darwin)
Alan Third <address@hidden> writes:

> I'm unsure what the purpose of this autorelease pool is. I guess it's
> supposed to be so that the dialog object always get released
> correctly, but it seems to be broken.
> I've just removed it, which I guess may introduce a memory leak, but I
> don't know how to check.

I've tried checking this with "leaks" and it's coming back clean, so
I've pushed it to master.
Alan Third

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]