Date: Thu, 11 Sep 2003 20:04:02 +0200 From: Morten Rodal <morten@rodal.no> To: deischen@freebsd.org Cc: David Xu <davidxu@freebsd.org> Subject: Re: libthr/libkse and Mozilla Firebird Message-ID: <20030911180402.GA1330@atlantis.rodal.no> In-Reply-To: <Pine.GSO.4.10.10309111352120.22524-100000@pcnet5.pcnet.com> References: <20030911140512.GA639@atlantis.rodal.no> <Pine.GSO.4.10.10309111352120.22524-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 11, 2003 at 01:57:22PM -0400, Daniel Eischen wrote: > On Thu, 11 Sep 2003, Morten Rodal wrote: > > On Thu, Sep 11, 2003 at 08:22:06AM +0800, David Xu wrote: > > > Did those saw Mozilla Firebird crashed test Mozilla as well ? > > > I used to use Mozilla, and never saw it crashed. > > > > > > > I just tested the Mozilla (www/mozilla-gtk2 ; mozilla-gtk2-1.4) port, > > and I can confirm that it too just disappears without a trace when run > > with libkse. It also, like Mozilla Firebird, freezes (not the > > computer, just the app) with libthr. > > Are you sure that your ports are correctly built (with -pthread > removal)? > I am pretty sure. I updated my ports tree before I compiled the Mozilla port. > I'm using www/mozilla & www/mozilla-firebird. > I am recompiling mozilla-firebird right now because I have a suspicion that it disables the core dump unless WITH_DEBUG is defined. > Is everyone that is having problems using NVidia cards? > Yes. I am using nvidia cards and have, as Maximi Konovalov(?), tried with both the nv and the nvidia driver. (Currently using nvidia driver tho) I did however get a something I've never seen before when a mozilla (not firebird) disappeard. I have not been able to reproduce this output, and google didn't turn up much either :/ --- The program 'mozilla-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 155 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) --- -- Morten Rodal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030911180402.GA1330>