Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Jun 2016 13:21:06 +0000
From:      Grzegorz Junka <list1@gjunka.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: Firefox 47.0 hangs when accessing cnn.com
Message-ID:  <e492f197-3789-0c4c-48d7-147f820e3aa3@gjunka.com>
In-Reply-To: <be669368-23d4-a173-6ecc-7a80442c2178@hiwaay.net>
References:  <20160606182103.GB55688@rancor.immure.com> <673bea9d889d59900f4a145334b07ca7@cyberbotx.com> <20160608000701.GA944@rancor.immure.com> <CAN6yY1t8yKv=TBqswnByKyvV4thHEQvgs1Pg_w14xgKXqtY%2BKA@mail.gmail.com> <20160608130741.GB944@rancor.immure.com> <20160608230452.GC944@rancor.immure.com> <CAN6yY1vXo_msofLB=DfTkkqF_RTKQHzT3spS_r-okiyeQ06rHw@mail.gmail.com> <be669368-23d4-a173-6ecc-7a80442c2178@hiwaay.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On 09/06/2016 13:10, William A. Mahaffey III wrote:
> On 06/09/16 00:10, Kevin Oberman wrote:
>> On Wed, Jun 8, 2016 at 4:04 PM, Bob Willcox < <kob6558@gmail.com>
>> bob@immure.com> wrote:
>>
>>> Ok, I finally figured out how to get portdowngrade to give me a 
>>> 46.0.1,1
>>> version of firefox and built & installed it. Unfortunately, that didn't
>>> solve
>>> my hanging firefox scripts problem so apparently it's likely to be 
>>> caused
>>> by
>>> something else that got updated when I did the portupgrade on June 
>>> 4th. Not
>>> sure where to go from here...
>>>
>>> Bob
>>>
>> No easy answers. I, also have no issues with 47.0 on my system and there
>> are no other reports of the problem you are having. So where to look?
>>
>> What version of FreeBSD are you running? On what platform? i386 or 
>> amd64 or
>> something else. Most people are running amd64. If ir is another 
>> platform,
>> issues are less likely to have been seen. Is it 10.3 or something else.
>>
>> Unless someone else has a better suggestion, I'd re-install all
>> dependencies. Older versions are more likely to have issues.I use
>> portmaster, but I know portupgrade can also do this. Or use packages. 
>> It's
>> a lot faster when you don't need any options on the ports.
>>
>> Other than that, I have no good ideas other than to re-install 
>> everything.
>> And that may not fix it as it is possible that it's a memory or other
>> hardware issue.
>>
>> I hope someone else has a better idea than I.
>> -- 
>> R. Kevin Oberman, Network Engineer, Retired
>> E-mail: kob6558@gmail.com
>> _______________________________________________
>> freebsd-ports@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>
>
> +1 on packages, *much* faster & same end result if you have no special 
> compile options ....
>
>

I second that and repeat what I said before. If you want to compile your 
own packages with custom options then fine, but do it properly with 
either poudriere or synth. Otherwise, just use the FreeBSD generic ones. 
Portupgrade and portmaster are fine but only as long as they work, and 
from my experience sooner or later they always stop working and from 
then there is going to be a path of misery, wasted time and broken 
applications.

Grzegorz



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e492f197-3789-0c4c-48d7-147f820e3aa3>