The problem is that after closing Chrome, it seems that it takes too long to close apparently, since the cursor indicates that there is something in process after closing it, and it stays like that for 15 seconds or more, sometimes less, but during that time I simply cannot open Chrome no matter how many times I click, not even if I open it through the terminal or start menu, I am in Xorg but, in Wayland it is the same or worse, It also happens with any other Chromium browser, regardless of whether it was installed via Deb or Flathub.
1 Like
Did You checked the System Monitor when that happens if there is something in action?
1 Like
Anything else that you can tell us about when this happens? For example, does it happen even when you don't have any tabs open? Are you doing other things with your computer that may be causing to run low on memory?
1 Like
I'd say that the system is slow to close all the processes that Chrome has run or it's taking time to save its data. So, while they're being closed it's impossible to reopen it.
It happens even when I only have one tab open, and even when I open it and immediately close it without having searched for anything, the strange thing is that it doesn't happen in Zorin Lite, but, I don't want to use Zorin Lite on a computer that in theory can run the Core version
I have 2 ideas 
, then nothing else in my mind for now 
:
toggle hardware acceleration on Chrome and restart it
with System Monitor, terminate Chrome and then reopen it, now kill it instead and reopen it
open System Monitor > Processes, 
Show dependencies on the options button (on the left of Minimize button), find Chrome on the list, close it and see if its processes close immediately or with a delay
In System Monitor, when I close Chrome, all the Processes related to Chrome disappear, but even if they are gone, I still have to wait several seconds to reopen it
And there are any other Processes what on high Ressource Consumption then?
No, in fact this happens even if I have the computer just turned on and nothing open, I have a good computer, an i7-8565U and 16GB of RAM with a new 256GB M.2, with that I rule out a performance problem I think.
1 Like
Might be other program running in the background or chrome's hardware acceleration feature may occasionally lead to issues.
1 Like
I guess one thing you can try is launch it through the command line. That should show some output as the program runs, but might show some useful details as to what's going on when you shut it down.
The exact command depends on whether the package is installed as a Debian or Flatpak package:
# For Debian packages
google-chrome
# For Flatpak
flatpak run com.google.Chrome
2 Likes
Hmm ... Hardware Acceleration in Chrome could be a Point. You could try it with active and non-active and look if You have a Difference.
You already tried it in Wayland and Xorg ...
What Power Profile do You use?
1 Like