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.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message