From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Sebastien Vauban" Newsgroups: gmane.emacs.bugs Subject: Re: bug#13546: 24.2.92; Error(s) when sending emails Date: Fri, 15 Feb 2013 17:33:19 +0100 Organization: Sebastien Vauban Message-ID: <86zjz5lepc.fsf@somewhere.org> References: <86ehh9mx93.fsf@somewhere.org> <861ud9gsh9.fsf@somewhere.org> <86ip5x3do6.fsf@somewhere.org> <86y5etph6t.fsf@somewhere.org> <86ip5wfv9u.fsf@somewhere.org> <86vc9winv5.fsf@somewhere.org> <86k3qcc65g.fsf@somewhere.org> <8638wzethn.fsf@somewhere.org> <86fw0z3z5e.fsf@somewhere.org> <86pq01oods.fsf@somewhere.org> <86k3q9mwwa.fsf@somewhere.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1360946107 30604 80.91.229.3 (15 Feb 2013 16:35:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Feb 2013 16:35:07 +0000 (UTC) To: bug-gnu-emacs-mXXj517/zsQ@public.gmane.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org-mXXj517/zsQ@public.gmane.org Fri Feb 15 17:35:29 2013 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 1U6OG0-0001QO-T1 for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 Feb 2013 17:35:29 +0100 Original-Received: from localhost ([::1]:57976 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U6OFh-00061N-9H for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 Feb 2013 11:35:09 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx05.eternal-september.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 67 Injection-Info: mx05.eternal-september.org; posting-host="56267169612f95d5ad2eeba965a549c1"; logging-data="31352"; mail-complaints-to="abuse-VVbKFVtnif8H+i2N2EyTrmui9UKz+5OX@public.gmane.org"; posting-account="U2FsdGVkX1+v5/IHWXV5rZPS2Cmv3d2X" User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2.91 (windows-nt) X-Archive: encrypt Cancel-Lock: sha1:qAR5FBkfgx58MJiCMxPVypQflB4= sha1:PQP6Go8QyZ5OX7vABm6pr7SpeoY= X-Url: Under construction... Original-Xref: usenet.stanford.edu gnu.emacs.bug:97641 X-BeenThere: bug-gnu-emacs-mXXj517/zsQ@public.gmane.org X-Mailman-Version: 2.1.14 Precedence: list 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-mXXj517/zsQ@public.gmane.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org-mXXj517/zsQ@public.gmane.org Xref: news.gmane.org gmane.emacs.bugs:71320 Archived-At: Eli, Eli Zaretskii wrote: >> From: "Sebastien Vauban" >> Cc: Sebastien Vauban , 13546-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org >> Date: Fri, 15 Feb 2013 16:15:01 +0100 >>=20 >> - What about that magical `C-v' character? Any idea? > > No idea. It doesn't seem to be related to the problem, though. > >> - Now that you know what the problem was, can you confirm that Emacs 23 = did >> behave well for my use case? Maybe Emacs 24.0 as well? > > Emacs 23 concealed the problem: it would let you continue invoking > subprocesses, but with every Locate subprocesses launched by Helm, > Emacs would leak 2 handles. After some time (longer than the 2-3 > hours you got with 24.2.9x), too many handles would have been lost, > and Emacs would become unusable. Moreover, since the OS cannot reuse > a process ID of a process which still has some handle open on it, the > entire system would become unusable, because it could no longer launch > processes. > > In v24.2.91, this handle leakage was plumbed, but doing so exhibited > another problem (which was already fixed on the trunk, btw), which > manifested itself in what you described. Note that this problem only > rears its ugly head whenever an async subprocess is launched and then > killed without letting it exit in an orderly manner. That is why no > one else reported the problem: I guess there are no more Helm users on > Windows who track the v24.3 pretests. > >> - Is the current problem only happening on Windows (or due to my shell >> setting)? > > It is specific to Windows, but is not related to any shell settings. > It happens every time an async subprocess is killed by calling > delete-process on it. > >> - Is it only with heavy process-creator users like me (by using Helm as = my >> almost only way to switch between buffers and files)? > > See above: delete-process is the main trigger. It prevents a slot > from being released in the array which Emacs on Windows uses to manage > subprocesses and network/serial connections. When all the 32 slots > are used up in this way, Emacs can no longer launch subprocesses or > open network connections. > > The code I added looks for these "lost" slots and releases them, so > that they can be reused. On the trunk, the problem is avoided > altogether, but that requires deeper changes in the related code, and > I'd rather not make them at this late stage of the pretest. > >> - Can you confirm the GDB command had to be "p *cp" and not "b *cp"? > > Yes, of course. Sorry. Thanks for these interesting explanations. Now, let's hope for the best! (and resolve Gnutls...=C2=A0;-)) Best regards, Seb --=20 Sebastien Vauban