> I feel like we are missing a trick here. Even with a relatively slow I/O
> device (I was faintly amused to see SSD in the list of relatively slow
> devices, if SSD is slow what is fast?) it should eventually catch up
> UNLESS something is generating an insane amount of I/O over a sustained
> peri
Hi.
On Thu, Jun 07, 2018 at 02:13:17PM -0400, Borden Rhodes wrote:
> > I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> > times fixed) bug that happens with relatively slow filesystem (be it
> > SSD/HDD/NFS or whatever) and a large amount of free RAM. I first
> >
On Thu, Jun 07, 2018 at 02:13:17PM -0400, Borden Rhodes wrote:
> > I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> > times fixed) bug that happens with relatively slow filesystem (be it
> > SSD/HDD/NFS or whatever) and a large amount of free RAM. I first
> > encountered t
> I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> times fixed) bug that happens with relatively slow filesystem (be it
> SSD/HDD/NFS or whatever) and a large amount of free RAM. I first
> encountered the thing back in 2.6.18 days, where it was presumably
> implemented (as
On Thu, 7 Jun 2018 05:38:20 -0400 Borden Rhodes said:
> I use KDE. That may be part of the problem.
>
> I can trigger OOM with only with a browser (Firefox or Chromium) open
> because it leaks memory on certain websites. Of course, I can trigger
> it more quickly with other programs like LibreOff
On Thu, 7 Jun 2018 11:48:54 +0300 Reco said:
> On Thu, Jun 07, 2018 at 11:05:27AM +0300, Abdullah Ramazanoğlu wrote:
> > On Thu, 7 Jun 2018 10:52:01 +0300 Reco said:
> >
> > [--8<--]
> >
> > > Limit the size of dirty blocks cache. Kernel defaults are insanely large.
> > > What I'm using here is
> Date: Thu, 7 Jun 2018 01:32:27 +0300
> The first questions regarding Out Of Memory situation is, how much memory do
> you have, and what Desktop Environment and active programs (other than the
> browser) have you been using when OOM-killer got triggered?
I use KDE. That may be part of the proble
Hi.
On Thu, Jun 07, 2018 at 11:05:27AM +0300, Abdullah Ramazanoğlu wrote:
> On Thu, 7 Jun 2018 10:52:01 +0300 Reco said:
>
> [--8<--]
>
> > I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> > times fixed) bug that happens with relatively slow filesystem (be it
>
On Thu, 7 Jun 2018 10:52:01 +0300 Reco said:
[--8<--]
> I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> times fixed) bug that happens with relatively slow filesystem (be it
> SSD/HDD/NFS or whatever) and a large amount of free RAM. I first
> encountered the thing back i
Hi.
On Wed, Jun 06, 2018 at 05:51:34PM -0400, Borden Rhodes wrote:
> On 6 June 2018 at 15:26, wrote:
> > Hi.
> >
> > On Tue, Jun 05, 2018 at 09:25:25PM -0400, Borden Rhodes wrote:
> >> During the freeze, hard drive activity goes through the roof. Yes, my
> >> hard drive is fine a
On 6 June 2018 at 15:26, wrote:
> Hi.
>
> On Tue, Jun 05, 2018 at 09:25:25PM -0400, Borden Rhodes wrote:
>> During the freeze, hard drive activity goes through the roof. Yes, my
>> hard drive is fine and works normally when doing anything else. I also
>> don't get these lockups when brows
Hi.
On Tue, Jun 05, 2018 at 09:25:25PM -0400, Borden Rhodes wrote:
> During the freeze, hard drive activity goes through the roof. Yes, my
> hard drive is fine and works normally when doing anything else. I also
> don't get these lockups when browsing in Windows.
That looks like an OOM-ki
This is a follow-up to a question I posted here on 27 May for which I
got no response. In it, I complained that my "new" laptop running
Buster completely freezes when browsing certain Javascript-heavy
websites (like Google Docs, Facebook and YouTube) on Firefox 52.
Since that e-mail, I installed C
13 matches
Mail list logo