From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Emacs crashes Date: Mon, 13 Mar 2006 23:06:33 +0100 Message-ID: References: <17429.54459.803236.351040@kahikatea.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1142295136 32633 80.91.229.2 (14 Mar 2006 00:12:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Mar 2006 00:12:16 +0000 (UTC) Cc: Nick Roberts Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 14 01:12:10 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FIx8l-0002p2-UW for ged-emacs-devel@m.gmane.org; Tue, 14 Mar 2006 01:11:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FIx8l-0004xi-Ac for ged-emacs-devel@m.gmane.org; Mon, 13 Mar 2006 19:11:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FIx8W-0004uw-OC for emacs-devel@gnu.org; Mon, 13 Mar 2006 19:11:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FIx8V-0004tp-BX for emacs-devel@gnu.org; Mon, 13 Mar 2006 19:11:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FIx8V-0004tZ-7Y for emacs-devel@gnu.org; Mon, 13 Mar 2006 19:11:39 -0500 Original-Received: from [193.162.153.10] (helo=pqueueb.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FIxCa-0008Fg-4P for emacs-devel@gnu.org; Mon, 13 Mar 2006 19:15:52 -0500 Original-Received: from pfepb.post.tele.dk (pfepb.post.tele.dk [195.41.46.236]) by pqueueb.post.tele.dk (Postfix) with ESMTP id 9C42E3DF142 for ; Mon, 13 Mar 2006 23:08:23 +0100 (CET) Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepb.post.tele.dk (Postfix) with SMTP id 0B884A50008; Mon, 13 Mar 2006 23:08:08 +0100 (CET) Original-To: emacs-devel@gnu.org In-Reply-To: <17429.54459.803236.351040@kahikatea.snap.net.nz> (Nick Roberts's message of "Tue, 14 Mar 2006 09:23:23 +1300") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:51580 Archived-At: Nick Roberts writes: > I've had Emacs crash/hang in three different ways in recent days. I can second that. I had another crash today, so it has crashed on me four times in the last week. I suspect the recent changes to the handling (unwind etc) of x errors, but I have no proof, as there is no similarity to the crashes (except that it has now crashed twice in malloc_consolidate (libc internal) called from emacs_blocked_malloc called from XtVaGetValues in x_set_toolkit_scroll_bar_thumb. I didn't have time to dig further into the crash - and I have no way to determine what kind of corruption was causing the crash in malloc_consolidate. > It would > appear to be less stable than it was two years ago: It *is* *much* less stable that it was a week ago! > > 1) It hangs with some kind of mutex lock which I don't understand with a brief > backtrace of three functions in libc, I think. The only thing I can do, > after attaching with GDB, is kill it. > > 2) A garbage collection related crash where mark_object is called recursively > literally thousands of times, > > 3) A crash that is caused by recent changes to the tool bar (I think). I > attach the bactrace to this one below (xbacktrace produces no output). > It appears to go wrong in produce_image_glyph where img=0x0 because > it->f->output_data.x->display_info->used = 73, is less than > it->image_id = 87. I haven't seen any of these -- so there are now 6 different crashes. Looks like a completely random memory corruption. -- Kim F. Storm http://www.cua.dk