From owner-freebsd-mozilla Tue Sep 14 20:57:22 1999 Delivered-To: freebsd-mozilla@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id C82D814C42 for ; Tue, 14 Sep 1999 20:57:19 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA18603; Tue, 14 Sep 1999 20:57:17 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd018576; Tue Sep 14 20:57:10 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA16678; Tue, 14 Sep 1999 20:57:06 -0700 (MST) From: Terry Lambert Message-Id: <199909150357.UAA16678@usr06.primenet.com> Subject: Re: Communicator 4.5: "Xlib: Unexpected async reply" msg flood! To: gsstark@mit.edu (Greg Stark) Date: Wed, 15 Sep 1999 03:57:01 +0000 (GMT) Cc: tlambert@primenet.com, denis@acacia.cts.ucla.edu, mozilla@freebsd.org In-Reply-To: <87vh9df47e.fsf@mit.edu> from "Greg Stark" at Sep 14, 99 07:44:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mozilla@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think this explanation really makes sense. Netscape doesn't actually > use the native threads, it uses some sort of user-space threads on all > platforms. > > It is the right basic idea though, "Unexpected async reply" and the "sequence > lost" both have to do with either a multi-threaded program calling Xlib > functions from two threads or a signal handler calling Xlib functions. > > Do you have further evidence about this involving freebsd native threads? Yes. The new InterJet II user interface (reviewed in PC Week Magazine, so I can talk about it) had to specifically be modified so that it would run the GIF downloads consecutively instead of concurrently to avoid crashing NetScape on both FreeBSD and Macintosh. The Microsoft Internet Explorer on Macintosh did not have the same problems, and it uses a binary GIF decoder wedged in via JNI (it is also significantly faster, as a result). There are still issues with the FreeBSD version of NetScape crashing if one moves the mouse over an image that will be used as an image map during download. Since it doesn't affect the Macintosh, it was felt that serializing the I/O further, which would result in an actual user perceptible slow down, at this point, was not worth it to obtain FreeBSD interoperability with the uder interface. The serialization soloution was arrived at by me, after observing the problem and non-problem platforms, and taking into account my detailed knowledge of threads implemetnations on Solaris, Linux, Windows 98, Windows NT, Macintosh, and FreeBSD. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mozilla" in the body of the message