On 17/03/20 07:17 -0500, Lucas Raab wrote: > On Tue, Mar 17, 2020, at 05:51, Stuart Henderson wrote: > > On 2020/03/17 09:25, Mikolaj Kucharski wrote: > > > On Tue, Mar 17, 2020 at 08:22:04AM +0000, Mikolaj Kucharski wrote: > > > > Do you see the same? I fails for me on anything which uses JavaScript I > > > > think. I'm using official packages on -current: > > > > > > I didn't need to wipe browser's cache for so long, that it didn't > > > ocurr to me something so obvious. Following command fixed the problem: > > > > > > rm -rf ~/.cache/chromium > > > > > > -- > > > Regards, > > > Mikolaj > > > > > > > If someone else hits this please try just removing > > > > ".cache/chromium/Default/Code Cache" > > > > and not the whole thing > > > > > > That worked perfectly for me > > Lucas >
We still do not know the reason behind this, but it is being worked on. -- Regards, Robert Nagy
