From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs does not listen on w32 Date: Mon, 14 Apr 2008 09:45:58 -0400 Message-ID: References: <4800D965.9080202@gmail.com> <480208C8.3030401@gnu.org> <480212F7.7090409@gmail.com> <4802249D.2060909@gmail.com> <480271D2.7040304@gmail.com> <4802FD64.1080602@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1208180812 2542 80.91.229.12 (14 Apr 2008 13:46:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Apr 2008 13:46:52 +0000 (UTC) Cc: Juanma Barranquero , Eli Zaretskii , jasonr@gnu.org, emacs-devel@gnu.org To: "Lennart Borgman \(gmail\)" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 14 15:47:26 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JlP1T-00009j-OU for ged-emacs-devel@m.gmane.org; Mon, 14 Apr 2008 15:47:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlP0p-00033l-96 for ged-emacs-devel@m.gmane.org; Mon, 14 Apr 2008 09:46:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JlP0j-000334-Dt for emacs-devel@gnu.org; Mon, 14 Apr 2008 09:46:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JlP0e-00030T-8L for emacs-devel@gnu.org; Mon, 14 Apr 2008 09:46:13 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlP0d-00030J-TO for emacs-devel@gnu.org; Mon, 14 Apr 2008 09:46:11 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JlP0R-0000Uy-Ri; Mon, 14 Apr 2008 09:46:00 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEADL9AkhMCqsI/2dsb2JhbACBXqg6 X-IronPort-AV: E=Sophos;i="4.25,655,1199682000"; d="scan'208";a="18472811" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 14 Apr 2008 09:45:59 -0400 Original-Received: from pastel.home ([76.10.171.8]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id URH10159; Mon, 14 Apr 2008 09:45:59 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id C22008A41; Mon, 14 Apr 2008 09:45:58 -0400 (EDT) In-Reply-To: <4802FD64.1080602@gmail.com> (Lennart Borgman's message of "Mon, 14 Apr 2008 08:44:52 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95178 Archived-At: >>> In any case, the first >>> thing to do is to figure out what *really* happened in the first place. >>> We don't even know why Emacs didn't respond. Maybe it has nothing to do >>> with the processing of WM_CLOSE. >> >> I don't think the problem was related to WM_CLOSE. What you suggested >> is much more likely: a memory leak. Windows tends to be *extremely* >> unresponsive on low-memory situations. > I think you and Stefan are right about the memory problem but that there are > two different problems. In response to Eli's message I tested a simple loop, > something like > (let (x y) > (while (not x) > (setq y (current-time-string)) > (when (string= y "something") > (setq x t)))) > Running this Emacs does not hang the pc, but it still does not answer when > clicking the [X]. (I could kill it with C-g here though.) Yes, that's perfectly normal. The current semantics of WM_CLOSE (for Emacs) is more or less the same as C-x C-c (or C-x 5 0): it waits for the current command to finish and then runs another command that deletes the frame. Stefan