Dennis Lee Bieber  wrote:
> On Thu, 19 Nov 2020 21:21:42 -0000 (UTC), bob prohaska 
> declaimed the following:
>
>>Has anybody else noticed this error message when using the Chromium
>>browser? I happen to be using a P4, if that matters. It appeared after
>>updating today, 11/19/2020, while reading the New York Times website.
>>Reports go back a few months, but nothing in the way of a fix.
>>
>
>         Well, the most informative report I've seen mentions the
out-of-memory
> killer in the OS. Have you tried monitoring memory usage (run top in a
> console window)?
>
>         Which R-Pi are you using?
An 8GB Pi4
>         Do you have a swap file on external media?
There's a 4GB hard partition, so far usage is nil.
Memory use tops at under 1.5GB

Since the original post I've noticed another problem, YouTube videos won't
start playing at 1080p, but if resolution is lowered to 480p momentarily
playback starts. Resolution can then be increased to 720p and will continue.
Whether this has anything to do with the error code is unclear, and doubtful.

In the meantime I found
https://support.google.com/chrome/thread/15650264?hl=en
which suggests turning off chrome://flags/#enable-quic
That's helped, but I've seen the error code since, so it's
not a cure entirely. But, it's a thread from 10/24/19
and the problem I'm seeing is brand new as of today.
It could be the nytimes.com website doing something wrong.....
For the moment I can't reproduce the "aw snap" error in the
subject line. It's odd I found that page at all, none of the
keywords in my search seem to match.

The 1080p playback stoppage seems to persist.

Thanks for reading!

bob prohaska

--- SoupGate-Win32 v1.05