[TriLUG] Strange lockups on Fedora

[Dwain Sims via TriLUG]

Peter:

Thanks for the reply.  Your observation on Videos with FF is interesting.
That could be the issue that I am seeing.

As an experiment, I will make sure no video happens on FF for the
foreseeable future.  I will keep that function on Chrome or Opera.

We might get to the bottom of this eventually.

Thanks

Dwain


On Fri, Jan 26, 2018 at 1:01 PM, Peter Neilson <neilson at windstream.net>
wrote:

> I'm using Ubuntu 14.4, and I stopped using FF, and am sticking with Chrome
> and Opera, and now have fewer problems. Still need to shoot the whole thing
> down every few days. If I don't watch videos it'll stay up forever.
>
> My wife's running 12.4, FF and occasionally Opera, and she'll occasionally
> tell me, "Could you please shoot down FF for me?" Sometimes it's gone to
> CPU hog, other times to no swap space. kill -9 is the solution!
>
> My wife watches videos on my machine, under Chrome, because hers won't
> deal with them well at all.
>
> Maybe some day I'll get around to trying to update the machines to more
> recent hdw and Ubuntu. But not today.
>
>
> On Fri, 26 Jan 2018 12:19:16 -0500, Dwain Sims via TriLUG <
> trilug at trilug.org> wrote:
>
>
>>> Subject: Re: [TriLUG] Strange lockups on Fedora
>>> Yes, I’ve seen this happen with the New Firefox as well on F27.  Either
>>> updates to FF or updates to F27 fixed it for me.
>>> Matt P.
>>>
>>
>>
>> I have seen this same behavior with the  "Web Content" process and the
>> whole lockup business.  Can happen out of the blue, but more likely over
>> the course of time.  It behaves like FF is leaking memory badly, and at
>> some point it gushes out.
>>
>> I was a little concerned that this was a hardware issue, but you folks
>> seeing it as well gives me more confidence that this is a software bug.
>>
>> I upgraded Mint from 18.1 to 18.3, and the incidents of this happening
>> have
>> diminished greatly, but not totally.  (I think I have had one lockup since
>> the upgrade.)
>>
>> In one case I was able to kill FF when it started to go off the rails and
>> that righted the ship, so to speak.
>>
>> Maybe what I should do is stick with Chrome and Opera and see if this goes
>> away completely.
>>
>> Dwain
>>
>