Date: Thu, 22 Sep 2016 10:06:46 +0200 From: Ralf Mardorf <ralf.mardorf@rocketmail.com> To: freebsd-questions@freebsd.org Subject: Re: firefox crash Message-ID: <20160922100646.26ef2406@archlinux.localdomain> In-Reply-To: <1bce8b64-b993-6e1e-2fee-f7c3cfe0c4ca@netfence.it> References: <d5cb94ad-9dc0-7102-1f58-cd6eedb72521@hiwaay.net> <20160919172525.2857fcee@archlinux.localdomain> <de6d50e8-f63e-d303-4075-f8fe3dd13c00@hiwaay.net> <20160920053641.e9075ee2.freebsd@edvax.de> <810b54d9-9769-eb99-8809-ea22a09f6d65@hiwaay.net> <1e50daef-c0e6-813b-2295-be8d413b4eb5@hiwaay.net> <20160921075019.3e68d68b@archlinux.localdomain> <1bce8b64-b993-6e1e-2fee-f7c3cfe0c4ca@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Sep 2016 09:41:05 +0200, Andrea Venturoli wrote: >On 09/21/16 07:50, Ralf Mardorf via freebsd-questions wrote: >> Hi, >> >> the OP seemingly is not affected, but assuming somebody searches the >> archive and should care about "firefox crash" and should be running >> FreeBSD 10.3 i386: >> >> https://lists.freebsd.org/pipermail/freebsd-multimedia/2016-September/017278.html > >THANK YOU VERU MUCH!!! > >I've had Firefox crashing constantly: I've suspected it to be an >i386-only problem, I suspected it was an issue with some dependency, I >recompiled everyhing with debug support without being able to get a >useful trace anyway, I asked on the list without getting any helpful >hint, finally could not get to the root cause until you suggested the >above! > >I've also tried finding a better (less worse?) browser than Firefox, >but until now could not achieve this. You noticed the follow-up? Begin forwarded message: Date: Wed, 21 Sep 2016 12:03:28 +0200 Subject: Re: FreeBSD Port: multimedia/ffmpeg On Wed, Sep 21, 2016 at 01:07:30AM -0400, Robert Burmeister wrote: > FreeBSD 10.3 i386 > multimedia/ffmpeg 2.8.8,1 > still crashes on i386 [Bug 204354] / [Bug 205958] > As Firefox now uses FFMPEG exclusively instead of gstreamer, > this bug is becoming impractical to work around. Well, a practical workaround is always to build the port yourself using different OPTIONs :-) Jokes aside, your point is of course valid. It seems there are still a large enough number of i386 CPUs in production that can't work with the SSE/SSE2-optimisations in ffmpeg. We might need to drop these optimisations in the set of default OPTIONs on i386. In your particular case: What exact CPU is this? Could you confirm that building an ffmpeg package without the SSE OPTION resolves the issue for you? Thanks and best regards Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160922100646.26ef2406>