Fedora: Google Chrome Oddity
-
-
@gjacobse If you setup a VM with the same version of Fedora and Chrome does this occur?
Why not try removing chrome and reinstalling, it's only a few commands.
-
Happened here while working on Pi - full screen takes only the half screen but horizontally.
Anyway on an seperate note If you have 8 GB of RAM you cant use Chrome anymore. on Linux it is insane Chrome eats 6.9 GB out of my 8 GB and when I close chrome i see htop giving me 500 MB used ram out of 8. Switched to FF, and it is more sane RAM usage and that peaks on ~5GB
-
@Emad-R chrome uses that much ram on your system?
-
@Emad-R said in Fedora: Google Chrome Oddity:
Happened here while working on Pi - full screen takes only the half screen but horizontally.
Anyway on an seperate note If you have 8 GB of RAM you cant use Chrome anymore. on Linux it is insane Chrome eats 6.9 GB out of my 8 GB and when I close chrome i see htop giving me 500 MB used ram out of 8. Switched to FF, and it is more sane RAM usage and that peaks on ~5GB
How many extensions are you running? Clean the cruft out and it'll tone itself down.
-
@DustinB3403 said in Fedora: Google Chrome Oddity:
@gjacobse If you setup a VM with the same version of Fedora and Chrome does this occur?
Why not try removing chrome and reinstalling, it's only a few commands.
This is my laptop.. no need for a VM
-
@gjacobse said in Fedora: Google Chrome Oddity:
@DustinB3403 said in Fedora: Google Chrome Oddity:
@gjacobse If you setup a VM with the same version of Fedora and Chrome does this occur?
Why not try removing chrome and reinstalling, it's only a few commands.
This is my laptop.. no need for a VM
The VM would be to just have something to test with that isn't your system.
-
Same thing after un/install... sigh.. well,.. it's reported as (unstable) for the platform anyway..so what-ev..
-
@gjacobse said in Fedora: Google Chrome Oddity:
Same thing after un/install... sigh.. well,.. it's reported as (unstable) for the platform anyway..so what-ev..
Huh. . . okay well I guess we found the problem then
-
I’ve only witnessed that with Firefox on Gnome3 Wayland and xorg.
