Tentative suggestion that this could be a duplicate of  issue 712166 . It seems very similar.

I don't experience unresponsiveness myself, but that may be because I'm on such an old machine everything's just slow all the time.

In response to comment one and notes on the reference report... yes, in most cases the HDD light is lit up solid. I used iptop to monitor and can also confirm the rates specified in the other report, 150-250 is what I see while the other user experiences 100-300KB/s.

My Chrome is 64 bit, if that makes a difference. I can also say for sure the process is named "[Chrome_HistoryT]" showing this activity, and most often, id prefaced by "chrome" to show "chrome [Chrome_HistoryT]". Sometimes, the "chrome" prefix is different, but not too often.

Please reference my post in the product help forums (https://productforums.google.com/forum/#!topic/chrome/So0l4navzeE) and also the post I referenced within:
https://productforums.google.com/forum/#!topic/chrome/zsk8TFvL7oM

Hope this provides a bit more detail and supporting information.

Unable to reproduce the issue on reported version 62.0.3202.18 stable version 61.0.3163.79 and latest Canary 63.0.3218.0 using Ubuntu 14.04.
Attaching screenshot for reference

 As the issues looks to be specific to Ubuntu 17.04 hence looping MTV team to check the same on Ubuntu 17.04

Deleted: Chrome_history.png 226 KB

	Chrome_history.png 226 KB View Download

Chrome_HistoryT is probably Chrome_HistoryThread. Although it's presumably also to be expected that Chrome loads stuff from the history database. It's on a different thread so it's not supposed to block the UI, though it sounds like in this report it is?

IF that question is for me, I am a bit unsure of what you are asking. The I/O from said process causes the system to work very slowly, whether that be Chrome or anything else. The HDD indicator on the computer remains almost solid lit throughout the process. It also does not pull back for other processes that should (I believe) have higher priority.

This issue started not too long ago. I cannot recall exactly when, but it was only a few months, maybe 2 or 3 is a reasonable guess. The process may well have been there before, but the issues reported here were not there as a result.

In most general terms, when this process begins running, best to give leave the computer until it is done. It does not throttle back as a result of user activity or anything. Most often, it just causes everything to run very slowly. On some more rare times, it will cause a crash and in one case for me, caused (I assume) network-manager to drop the wireless connection. I assume this because it happened while said process was running and no other devices lost connection. The following command corrected the network issue immediately, once I was able to open terminal.

sudo service network-manager restart

This is an image to show where I have identified the process causing the issue experienced. I kept this one as it shows that only Chrome is involved in I/O, so me seeing the HDD light on solid is most likely due to the process(s) indicated here. You can see the process as I have identified utilizing 183, where I have stated it is normal between 150 and 200. I share as this is a great illustration of what I am seeing.

Deleted: Screenshot at 2017-09-23 05-15-24.png 96.3 KB

	Screenshot at 2017-09-23 05-15-24.png 96.3 KB View Download

Is there anything I can do to help on resolving this?

RE: As the issues looks to be specific to Ubuntu 17.04 hence looping MTV team to check the same on Ubuntu 17.04

I have been using Ubuntu 17.10 since release day, this issue is still the same, no change except it is taking longer for it to allow me to use the computer again. I have still found no way to easily stop this, I can close Chrome (including the run in background in task bar) and it will still run. From there, killing the processes for Chrome will do it, but it takes a bit for the final process to actually stop running.

This process that runs is intrusive and persistent, and will not yield to user activity. Given that this is starting to make Chrome non-usable, is there a way I can just stop this process/task from running? I am still unsure what it is, but nothing for a browser needs to run multiple times a day and basically take control of the whole system for a good part of an hour each time. I am sure I can do without whatever this is and/or is doing.

Traduire la page en français

Le 4 déc. 2017 05:58, "brianjz… via monorail" <
monorail+v2.4063521929@chromium.org> a écrit :

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot