From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: emacs 23.1 not responding, known bug? Date: Sun, 1 Nov 2009 13:52:31 +0100 Message-ID: References: <2a382c6e0911010437s7ec007bbuf920a335657f842d@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1257079991 18201 80.91.229.12 (1 Nov 2009 12:53:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 1 Nov 2009 12:53:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dave Milter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 01 13:53:04 2009 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 1N4Zvb-0006sk-He for ged-emacs-devel@m.gmane.org; Sun, 01 Nov 2009 13:53:03 +0100 Original-Received: from localhost ([127.0.0.1]:34658 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N4Zva-0006fN-Pf for ged-emacs-devel@m.gmane.org; Sun, 01 Nov 2009 07:53:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N4ZvV-0006f7-3T for emacs-devel@gnu.org; Sun, 01 Nov 2009 07:52:57 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N4ZvQ-0006eY-OA for emacs-devel@gnu.org; Sun, 01 Nov 2009 07:52:56 -0500 Original-Received: from [199.232.76.173] (port=44520 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N4ZvQ-0006eV-IL for emacs-devel@gnu.org; Sun, 01 Nov 2009 07:52:52 -0500 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:38665) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N4ZvQ-0008Cu-4a for emacs-devel@gnu.org; Sun, 01 Nov 2009 07:52:52 -0500 Original-Received: by ywh32 with SMTP id 32so3998965ywh.14 for ; Sun, 01 Nov 2009 04:52:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=bKNagmDw2+0Ixau1l54m0KibeU86tF3yCcIauLYKzao=; b=Eq9NwTMMMMaVtx2FTNJP/JWkNk9KSKU16+QX6CSF8WyL/oJLdxXGM4F9o8rPsIJVL5 oxrJzZIsHxUeXOFGpjxFYjFweFSeUKcM0j5QNiMCzLyGpiEtIPAm0WSwD8JH/ymthfM+ iSi5XAH2JkA3gC3pCDKlSLUsy/zuvU4z3KBD0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=Ne+HxxUVpQ+zFO8LlbYHygRbILlM6oZgtFKj0OvM+JhN4E8m4LlmOy+8ZGAaD2g+JG o6nExghgOB6GkF/rWp8KRZBbIL4asSntuahlvhBuVZFXFGboTOlrCl9GGC7uKs8sp1f6 fHfyCy25PNV0XndNcCLKSSpb+OhEFFDrCDPUY= Original-Received: by 10.100.20.22 with SMTP id 22mr2571317ant.43.1257079971095; Sun, 01 Nov 2009 04:52:51 -0800 (PST) In-Reply-To: <2a382c6e0911010437s7ec007bbuf920a335657f842d@mail.gmail.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:116552 Archived-At: On Sun, Nov 1, 2009 at 1:37 PM, Dave Milter wrote: > After update to 23.1, > I time to time see the same behaviour, emacs not responding to key presse= s, > and eats CPU like a pig, > ctrl+g =C2=A0only helps to return responding by a second, then it again e= ats CPU. > if connect gdb to emacs it show that it hangs in mark_object function. > > Several people told me that they see the same behaviour, but they advise = me > just stop use 23 branch and return back to 22. May be there is another so= lution? Since many people are using 23.1 there must be something more specific that causes the problem. Can you please give us more details? Can you reproduce the problem starting from a bare bone Emacs (emacs -Q)?