From owner-freebsd-current Sun Jul 29 7:29:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by hub.freebsd.org (Postfix) with ESMTP id 687A337B403 for ; Sun, 29 Jul 2001 07:29:29 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com ([202.108.25.152] (may be forged)) by neptune.he.net (8.8.6/8.8.2) with ESMTP id HAA29029 for ; Sun, 29 Jul 2001 07:29:29 -0700 Received: (from robinson@localhost) by netrinsics.com (8.11.2/8.11.1) id f6TETe100733 for current@outbound.freebsd.org; Sun, 29 Jul 2001 22:29:40 +0800 (+0800) (envelope-from robinson) Date: Sun, 29 Jul 2001 22:29:40 +0800 (+0800) From: Michael Robinson Message-Id: <200107291429.f6TETe100733@netrinsics.com> To: current@freebsd.org Subject: X in free(): error: recursive call. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am running -CURRENT as of 2001/01/31 12:00, more or less uneventfully for the last six months on a Dell 5000e. The one problem is that X occasionally dies without coredump or cleanup with the error 'X in free(): error: recursive call.'. This usually (but not always) happens while using Mozilla with heavy window creation/deletion and heavy (dialup) network activity. This has happened under several recent versions of Mozilla, two different versions of fvwm2, with and without session managers, and with both X 4.0.3 and 4.1.0. It took me a while to identify the problem, because it happens infrequently, unpredicably, and leaves the video drivers in an unusable state (forcing a blind reboot). I tried linking /etc/malloc.conf to 'A' to get a coredump from X, but that doesn't work. I found a very short discussion of a related problem in the -CURRENT mail archives from the beginning of January, but there wasn't any apparent resolution of the problem. I'd like to get advice on which of the following courses of action to take: 1. Isolate and fix the problem. I would need some help here. 2. Downgrade to -STABLE. The reason I was running -CURRENT originally was for ACPI support, but Dell has since released an APM-enabled BIOS for the 5000e, so -CURRENT is no longer a requirement. 3. Upgrade to current -CURRENT. I don't know if this is such a good idea judging from mailing list traffic. 4. Hang in with the status quo for another couple months until 5.0 is released, install that, and start back at #1 if that doesn't work. Any advice, comments, or suggestions warmly appreciated. Thanks. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message