Re: Other browsers show the same behaviour (Firefox crashes on yahoo.com)
On Sat, Jun 27, 2009 at 11:01 AM, Morgan
Wesström wrote:
>
> I'm not using X at all on my FreeBSD machines so I don't know if this is
> related. We had a similar problem in Gentoo lately where Firefox simply
> segfaulted on certain webpages. It was tracked down to librsvg and there
> is a temporary patch for 2.22-2.26:
> http://mirrors.evolva.ro/gentoo-portage/gnome-base/librsvg/files/librsvg-2.22.3-fix-segfault-with-firefox.patch
> As I said, I don't know if this relates to FreeBSD in any way but to a
> layman like myself it seems plausible since it's the same applications
> involved and I can't see that there is a patch for this in Ports. Some
> developer probably can make more sense out of this than I but I though
> it was worth mentioning.
>
I didn't see any replies about ${OTHER_OS} -- Firefox 3.0.11 does not
crash on *buntu (don't ask) for me. I just wanted to point that out.
I don't have FF3 on FreeBSD boxes to test.
Just thought I'd share.
--
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Other browsers show the same behaviour (Firefox crashes on yahoo.com)
On Saturday 27 June 2009 06:41:43 Manish Jain wrote: > The problem is not restricted to firefox or yahoo.com. There are other > sites too where this happens. I built Galeon from ports, and it shows > exactly the same behaviour as firefox2/firefox3 for those sites. So does > Epiphany (installed from the distribution media). Galeon also uses mozilla engine. How about Opera? > >> The program 'firefox-bin' received an X Window System error. > >> This probably reflects a bug in the program. > >> The error was 'BadImplementation (server does not implement operation)'. > >> (Details: serial 31 error_code 17 request_code 140 minor_code 5) > >> (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.) > >> > >> [1]+ Exit 1 firefox3 http://www.yahoo.com > > > > There is nothing relevant to the crash in Xorg.0.log or console.log Yet, could you startup firefox with --sync to see where it crashes? Unable to reproduce here. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Other browsers show the same behaviour (Firefox crashes on yahoo.com)
Manish Jain wrote: > The problem is not restricted to firefox or yahoo.com. There are other > sites too where this happens. I built Galeon from ports, and it shows > exactly the same behaviour as firefox2/firefox3 for those sites. So does > Epiphany (installed from the distribution media). > > >> Hi, >> >> This seems to be a strange problem with Firefox which I never >> encountered on my old system. Both Firefox2 and Firefox3 work well the >> other sites I have tried accessing, but crash on navigating to >> www.yahoo.com >> >>> /usr/home/emmjanex # firefox3 http://www.yahoo.com & >>> [1] 2668 >>> /usr/home/emmjanex # NP_Initialize >>> New >>> SetWindow >>> SetWindow >>> NewStream >>> WriteReady >>> Write >>> decoding... >>> The program 'firefox-bin' received an X Window System error. >>> This probably reflects a bug in the program. >>> The error was 'BadImplementation (server does not implement operation)'. >>> (Details: serial 31 error_code 17 request_code 140 minor_code 5) >>> (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.) >>> >>> [1]+ Exit 1 firefox3 http://www.yahoo.com >> >> >> There is nothing relevant to the crash in Xorg.0.log or console.log > I'm not using X at all on my FreeBSD machines so I don't know if this is related. We had a similar problem in Gentoo lately where Firefox simply segfaulted on certain webpages. It was tracked down to librsvg and there is a temporary patch for 2.22-2.26: http://mirrors.evolva.ro/gentoo-portage/gnome-base/librsvg/files/librsvg-2.22.3-fix-segfault-with-firefox.patch As I said, I don't know if this relates to FreeBSD in any way but to a layman like myself it seems plausible since it's the same applications involved and I can't see that there is a patch for this in Ports. Some developer probably can make more sense out of this than I but I though it was worth mentioning. Regards Morgan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Other browsers show the same behaviour (Firefox crashes on yahoo.com)
The problem is not restricted to firefox or yahoo.com. There are other sites too where this happens. I built Galeon from ports, and it shows exactly the same behaviour as firefox2/firefox3 for those sites. So does Epiphany (installed from the distribution media). Hi, This seems to be a strange problem with Firefox which I never encountered on my old system. Both Firefox2 and Firefox3 work well the other sites I have tried accessing, but crash on navigating to www.yahoo.com /usr/home/emmjanex # firefox3 http://www.yahoo.com & [1] 2668 /usr/home/emmjanex # NP_Initialize New SetWindow SetWindow NewStream WriteReady Write decoding... The program 'firefox-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadImplementation (server does not implement operation)'. (Details: serial 31 error_code 17 request_code 140 minor_code 5) (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.) [1]+ Exit 1 firefox3 http://www.yahoo.com There is nothing relevant to the crash in Xorg.0.log or console.log -- Regards Manish Jain invalid.poin...@gmail.com +91-96500-10329 Laast year I kudn't spell Software Engineer. Now I are won. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
