On 11/23/23 17:37, Michael Hennebry wrote:
On Thu, 23 Nov 2023, Samuel Sieb wrote:
> On 11/23/23 17:12, Michael Hennebry wrote:
>> On Thu, 23 Nov 2023, Samuel Sieb wrote:
>>
>>> Have you checked the journal? I had this happen on a computer that
>>> definitely wasn't low on memory and the journal had a bunch of
>>> messages from firefox about timeouts.
>>
>> journalctl and then what?
>
> I used "journalctl -r" which will display lines reversed starting from
> the most recent. Or you can run "journalctl -b" and press "G" to
go
> to the end. It uses the same navigation keys as "less".
I used journalctl -r -g irefox
Rather a lot of
... [Child 287536, MediaDecoderStateMachine #1] WARNING:
Decoder=7fde2015e400 Decode error:...
I suspect they relate to a video I was trying to watch.
Did not see anything that seemed to be a memory thing.
Possibly related, I'm also getting issues where typing doesn't work for
a long time with the following messages in the log:
firefox.desktop[2327]: [Parent 2327, Main Thread] WARNING: Process Key
Event failed: Timeout was reached.: 'glib warning', file
/builddir/build/BUILD/firefox-120.0/toolkit/xre/nsSigHandlers.cpp:187
firefox[2327]: Process Key Event failed: Timeout was reached.