From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: emacsq Newsgroups: gmane.emacs.help Subject: Re: What does the error "Process not running" mean? Date: Wed, 09 Feb 2022 12:55:27 +0000 Message-ID: References: =?us-ascii?Q?_<8jy--UTf4wNbxysxHArjzE3ADfF5mB=3D5FZsfnFd7sgKpf=3D5FGM=3D5F9O5YqVK1PH1QbnoizHbb6HonK-BeQEQx0OpCmSRnMSpJzNTcHHXASGOoiD9I=3D3D@protonmail.com>__<87pmny8nb4.fsf@gnu.org>_<=3D5FcUGEWwwd0FeA1-yUQ5OJfKvG6Y2m4lFHC0m42EOzULv02BYrQMv6BYH-YMsVim1q3G8b3ZNnmPMGB0ZgQP7=3D5F2Ib5vLqAHln3bVDUOqT3eU=3D3D@protonmail.com>__<87pmnx63uy.fsf@gmail.com>___?= Reply-To: emacsq Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18517"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Tassilo Horn , help-gnu-emacs@gnu.org To: Robert Pluim Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 09 14:28:34 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nHn1O-0004bq-2t for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 09 Feb 2022 14:28:34 +0100 Original-Received: from localhost ([::1]:39558 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nHn1M-0005HG-SL for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 09 Feb 2022 08:28:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48156) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nHmVT-0004x1-QE for help-gnu-emacs@gnu.org; Wed, 09 Feb 2022 07:55:36 -0500 Original-Received: from mail-40137.protonmail.ch ([185.70.40.137]:40411) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nHmVQ-0002Td-BW; Wed, 09 Feb 2022 07:55:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1644411328; bh=S2MUVEXBXWVTmHbvcPOikpAxnFUbkvuUjGfnQNF7CJA=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=GZ3LHBoAl6SfQEoOHZzhNSbXmGNKN6sJgWPJqcd6Dl9i447M3aww2sVJCDLYiiO9b j1OjepUCag0G8nS727K+q4cV526hco/tqfKqMVRE0zN7itTdk7q3W4voYKflz1SInn FYgYfcUcmVqxA/pndFYj4o/znK+H3EJPNVxy96zp854v/seAbaFYoU6bFGxnP2pT+f O/Z3RffbALw+fMlZZUF6UBXpL/lux6RnrJkhsFKnTvcx69GkfWLIZYNNRwOlaCzCTS PlR5i7F0epbFAdNKB9vVaJO5Q+5RFeZLx5RcYREqdktRqememvDVgRH6oHM/pd/t/1 WJ3YulTmXbAEw== In-Reply-To: Received-SPF: pass client-ip=185.70.40.137; envelope-from=laszlomail@protonmail.com; helo=mail-40137.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135865 Archived-At: > But in case of windows with the 32 process limitation it's > clearly a bug, because the lingering pocesses use up the > available sockets, so while the limit is there, these > processes should be closed when the callback is called. I tried adding process deletion before the callback: (defun url-http-activate-callback () (if (eq (window-system) 'w32) (delete-process url-http-process)) .... which seemed to work when fetching 1 url, it disappeared from list-processes, but when I fetched a few dozen urls then lots of processes stayed in the list with open status, despite deleting the processes before the callback. I used (setq url-queue-parallel-processes 1) with url queue for the test.