It sounds similar, but it's not. For one, the problem disappeared after the reporter restarted the computer; in my case the problem persists over many restarts and chrome/eset reinstallations. Second, disabling eset (pausing it) has no effect on the problem. Third, it's the memory that peaks not the cpu. Fourth, it started as of version 82.0.4083.0 of chrome and has worked perfectly well until then.