From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.help Subject: Re: It's almost 2016 and when (single-threaded) Emacs hangs, you gotta be smashing your keyboard! Date: Thu, 19 Nov 2015 23:25:55 +0200 Message-ID: <564E3E63.1010003@yandex.ru> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1447968381 8248 80.91.229.3 (19 Nov 2015 21:26:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2015 21:26:21 +0000 (UTC) To: Alexander Shukaev , help-gnu-emacs Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Nov 19 22:26:15 2015 Return-path: Envelope-to: geh-help-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 1ZzWib-0005gE-Bz for geh-help-gnu-emacs@m.gmane.org; Thu, 19 Nov 2015 22:26:13 +0100 Original-Received: from localhost ([::1]:44120 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzWia-0008Es-5R for geh-help-gnu-emacs@m.gmane.org; Thu, 19 Nov 2015 16:26:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzWiQ-0008Ec-5T for help-gnu-emacs@gnu.org; Thu, 19 Nov 2015 16:26:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzWiM-00062r-Qz for help-gnu-emacs@gnu.org; Thu, 19 Nov 2015 16:26:02 -0500 Original-Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]:38664) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzWiM-00062U-L9 for help-gnu-emacs@gnu.org; Thu, 19 Nov 2015 16:25:58 -0500 Original-Received: by wmec201 with SMTP id c201so135934971wme.1 for ; Thu, 19 Nov 2015 13:25:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=jbbgKMh8x+sPoMAklyyV7r8W73N5d5uZ057dP8qNtNc=; b=Lf+Moc2KHD9IrF7oRL9X9gskb/BR/Y2fxDejRqpPG5Di4PTTe901OXKBHsVxag1VMW 1ziY5YGAF+UmTtEAUqOf0lKKyXwMHtcIR5sN5IMhG2el688lb7BA5WcY19pDLFnVNpUR FvC8Ep8q6B2j2wFIuJDtVLu+htQ1ECqOfnjlh1N2xhwZEJCiFdgPk9W0igBUA4GzBgJv /ywG2f9yM1ZVwF9oXIEApBqhjQ0YB+hPbgcTGgkVRr7KeSSDkhB6i/zge17TpTcd4B40 khI4OAKc9VrEDexm+6EkejeZsaEMl22X/KXWyro+00q4IWluEwnJMXSJCSheibw/EnP6 YdnQ== X-Received: by 10.194.95.65 with SMTP id di1mr10357073wjb.134.1447968358154; Thu, 19 Nov 2015 13:25:58 -0800 (PST) Original-Received: from [192.168.1.2] ([185.105.175.24]) by smtp.googlemail.com with ESMTPSA id b82sm10843146wmf.9.2015.11.19.13.25.56 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Nov 2015 13:25:57 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c09::231 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:108149 Archived-At: On 11/19/2015 10:29 PM, Alexander Shukaev wrote: > The only > way to recover from such problems is to kill the Emacs process. Have you tried pressing C-g a few times? > I mean, seriously, > how can so advanced text editor with ~30 year history be so unreliable > and fragile to work with in randomly occurring cases? It may freeze > or it may not freeze, but if it does, all of the unsaved work is lost, > not to mention the fact that all of the layout of windows and open > buffers are lost as well. It's literally UNACCEPTABLE. How will multi-threading fix that? Sure, Emacs might keep working in the other buffers, but now you have a frozen/dead thread on your hands, which probably takes up 100% CPU. And if the UI is still working, you're free to create more frozen threads like that. As a rough guess, any proper solution to frozen threads of execution can also be applied to the current codebase.