From owner-freebsd-ports@FreeBSD.ORG Thu Dec 7 09:03:23 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 464D416A403 for ; Thu, 7 Dec 2006 09:03:23 +0000 (UTC) (envelope-from marko@freebsd.org) Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA70C43CB6 for ; Thu, 7 Dec 2006 09:02:30 +0000 (GMT) (envelope-from marko@freebsd.org) Received: from [80.229.231.20] (helo=[192.168.1.4]) by pih-relay05.plus.net with esmtp (Exim) id 1GsF9x-0008TJ-Mi for freebsd-ports@freebsd.org; Thu, 07 Dec 2006 09:03:18 +0000 Message-ID: <4577D8BE.6020105@freebsd.org> Date: Thu, 07 Dec 2006 09:02:54 +0000 From: Mark Ovens User-Agent: Thunderbird 1.5.0.7 (X11/20061107) MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Firefox & thunderbird crash saving a file X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 09:03:23 -0000 This started around the late 1.5.0.x versions and also happens in FF 2.0 When saving a file, e.g. an e-mail attachment, right-click->Save Link As... on a webpage, or uploading a file to a web forum, it will work once - maybe twice - but on subsequent saves the dialogue opens but the cursor stays as 'busy' for ~15 seconds, then FF/TB segfault and crash. % uname -a FreeBSD redshift 6.1-RC FreeBSD 6.1-RC #0: Mon May 1 14:05:04 BST 2006 root@redshift:/usr/obj/usr/src/sys/REDSHIFT i386 This is a stack trace of the core dump - both FF and TB give the same trace. (gdb) bt #0 0x28c0a1ab in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x28bf86dd in sigaction () from /usr/lib/libpthread.so.2 #2 0x28bf1c45 in pthread_kill () from /usr/lib/libpthread.so.2 #3 0x28bf14c4 in raise () from /usr/lib/libpthread.so.2 #4 0x08060134 in ?? () #5 0x0000000b in ?? () #6 0xbfbfb6d0 in ?? () #7 0x00000000 in ?? () #8 0x0806e048 in ?? () #9 0x00000400 in ?? () #10 0x00000000 in ?? () #11 0x00000000 in ?? () #12 0x00000000 in ?? () #13 0xbfbfb7b0 in ?? () #14 0x0000000f in ?? () #15 0x00000000 in ?? () #16 0x28c0d4b4 in ?? () from /usr/lib/libpthread.so.2 #17 0xbfbfba60 in ?? () #18 0x0000000b in ?? () #19 0xbfbfb728 in ?? () #20 0x28bf6598 in sigaction () from /usr/lib/libpthread.so.2 Previous frame identical to this frame (corrupt stack?) (gdb) total 19 What is very suspicious is the last line if the trace about a corrupt stack. Looks like it is a threading problem but since I can't find any other posts about this happening I guess it's just my system. Since my system is 6 months old (6.1-RC) do you think doing a make world to bring it up to 6.2 would solve the problem? Thanks. Regards, Mark