From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#20220: severe memory leak on emacs 24.4.1 Date: Wed, 01 Apr 2015 17:25:10 +0300 Message-ID: <83iodgrkmx.fsf@gnu.org> References: <83mw2vzui9.fsf@gnu.org> <551BA358.2000404@dancol.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1427898389 6476 80.91.229.3 (1 Apr 2015 14:26:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Apr 2015 14:26:29 +0000 (UTC) Cc: 20220@debbugs.gnu.org, mariovalspi@gmail.com To: Daniel Colascione Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Apr 01 16:26:19 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YdJay-0001LF-8k for geb-bug-gnu-emacs@m.gmane.org; Wed, 01 Apr 2015 16:26:16 +0200 Original-Received: from localhost ([::1]:52951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdJax-0001mO-Gq for geb-bug-gnu-emacs@m.gmane.org; Wed, 01 Apr 2015 10:26:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56672) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdJaq-0001iI-B3 for bug-gnu-emacs@gnu.org; Wed, 01 Apr 2015 10:26:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YdJak-00012A-Ml for bug-gnu-emacs@gnu.org; Wed, 01 Apr 2015 10:26:08 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:52801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YdJak-000122-I9 for bug-gnu-emacs@gnu.org; Wed, 01 Apr 2015 10:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YdJak-0001kX-9D for bug-gnu-emacs@gnu.org; Wed, 01 Apr 2015 10:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 01 Apr 2015 14:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20220 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20220-submit@debbugs.gnu.org id=B20220.14278983616717 (code B ref 20220); Wed, 01 Apr 2015 14:26:02 +0000 Original-Received: (at 20220) by debbugs.gnu.org; 1 Apr 2015 14:26:01 +0000 Original-Received: from localhost ([127.0.0.1]:42577 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YdJai-0001kH-Mb for submit@debbugs.gnu.org; Wed, 01 Apr 2015 10:26:00 -0400 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:44579) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YdJag-0001k3-RC for 20220@debbugs.gnu.org; Wed, 01 Apr 2015 10:25:59 -0400 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NM400900T1E9I00@mtaout25.012.net.il> for 20220@debbugs.gnu.org; Wed, 01 Apr 2015 17:20:33 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NM4004UFT69RH40@mtaout25.012.net.il>; Wed, 01 Apr 2015 17:20:33 +0300 (IDT) In-reply-to: <551BA358.2000404@dancol.org> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:101110 Archived-At: > Date: Wed, 01 Apr 2015 00:50:48 -0700 > From: Daniel Colascione > CC: 20220@debbugs.gnu.org > > Do we need the lisp thread to be the main thread? What about calling > CreateThread very early in initialization with a large dwStackSize, > leaving other threads with default-sized stacks? Might be possible, I don't know. For example, does any of the code make any hidden assumptions that the Lisp thread is the main thread? And in any case, if threads are created for each invocation, and never die as long as Emacs runs, then sooner or later Emacs will run out of address space and/or handles (I see on that single system where I can reproduce the problem that each such thread consumes 2 handles, and I don't see it exit). So it sounds like trying to find and fix the reason(s) for this rare behavior, or find a workaround (other than not using the API) is a better alternative, at least at this point.