From owner-freebsd-mozilla Fri Apr 30 2:35:41 1999 Delivered-To: freebsd-mozilla@freebsd.org Received: from acacia.cts.ucla.edu (acacia.cts.ucla.edu [164.67.62.44]) by hub.freebsd.org (Postfix) with ESMTP id BFEFB1590E; Fri, 30 Apr 1999 02:35:38 -0700 (PDT) (envelope-from denis@acacia.cts.ucla.edu) Received: from localhost (denis@localhost) by acacia.cts.ucla.edu (8.9.2/8.8.8) with ESMTP id CAA00787; Fri, 30 Apr 1999 02:37:55 -0700 (PDT) (envelope-from denis@acacia.cts.ucla.edu) Date: Fri, 30 Apr 1999 02:37:55 -0700 (PDT) From: Denis DeLaRoca To: questions@freebsd.org, mozilla@freebsd.org Subject: Communicator 4.5: "Xlib: Unexpected async reply" msg flood! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mozilla@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this problem occur with both the FreeBSD version of Communicator 4.5 in the packages collection as well as with Communicator 4.51 for Linux under FreeBSD 3.1. At some point, a popup appears with the following message, Bookmarks have changed on disk. Discard your unsaved changes and reload OK CANCEL Most of the time clicking on Ok or CANCEL allows one to continue normally... but at other times, Communicator starts looping and outputting messages to stderr that read Xlib: Unexpected async reply (sequence 0x####) the messages -- with increasing sequence numbers -- are displayed in pop up windows that quickly flood most of the Window Manager's desktop. The only way to recover from this is by killing the Communicator processes that at this point are chewing close to 100% of the CPU. What is going one? Any workarounds to avoid or fix this situation? -- Denis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mozilla" in the body of the message