Hacker News

Chrome AI features wasting much bandwidth

92 points by speckx ago | 33 comments

xnx |next [-]

I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".

bikeshaving |root |parent |next [-]

This is probably just Chrome redownloading the weights. But there is a fringe possibility that the local model is getting hijacked for inference, or even more sci-fi, that it’s being corrupted by some sort of rogue global botnet.

When I read about Chrome shipping local weights in every computer I can’t help but be reminded of the Great Cannon, where a MITM code injection by China caused end-user browsers to launch a DDOS on GitHub back in 2015. What could an AI adversary do with a fraction of Chrome’s local models, I wonder.

https://en.wikipedia.org/wiki/Great_Cannon

refulgentis |root |parent [-]

> This is probably just Chrome redownloading the weights.

Why do we think that?

I'm not getting specific because I think people are ragging on Chrome too much or whatever.

I'm really alarmed that Chrome could eat 100s of GBs a month and people are handwaving about the cause(s?) in a way that shades rather than illuminates.

autoexec |root |parent |next |previous [-]

> I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".

What else, going on with this guy's computer, would cause that volume of traffic to immediately stop as soon as he "disabled everything on that settings page"?

It may not be happening to you if you've got all that crap enabled, but that doesn't mean it wasn't happening to him. Companies love to single out subsets of their userbase and secretly experiment on them. When something goes wrong users get gaslighted by other people who say "I never see that happen!" or "It works fine for me!". Who the hell knows what Google and their AI was doing on this guy's computer. I'd put more trust in a random web developer on the internet than I'd trust Google.

|root |parent |next [-]

jeffbee |root |parent |previous [-]

"Hundreds of GB per month" is, at least, 70KB/s, which should be pretty easy for anyone to observe. So is your Chrome doing it?

My hypothesis is this guy installed so many shady ad blockers and VPNs that were using his rig as a proxy, and the cessation of such traffic, whether permanent or temporary, was purely coincidental.

pixl97 |root |parent [-]

Your take is 'probably' correct.

The problem here is without a deep dive you just don't know. Google likes A/Bing the shit out of their software. Google loves setting all kinds of different options that may have to be replicated exactly to get the same behavior.

This isn't like support back in the old days where you just look at your software and find the bug, you have to replicate the environment to see what's up.

jeffbee |root |parent |next [-]

OK but the OP provided zero evidence. Chrome has chrome://net-export/ for a reason. Show us logs.

simlevesque |root |parent |next |previous [-]

> The problem here is without a deep dive you just don't know.

Without knowing, you don't accuse.

jorvi |root |parent |previous [-]

Spotify had a bug where it was writing ten to hundreds of GB to people their SSDs, each day. HN refused to believe it until Spotify acknowledged it. "You must have just injected some shady JavaScript mod".

jeffbee |root |parent |previous [-]

"Don’t take my word for it." - agreed

skullone |next |previous [-]

I seriously doubt this. Show your logs, otherwise this is worthless blog spam

josephernest |next |previous [-]

I have another problem with Chrome AI features.

Sometimes I notice my PC being very very slow... The Chrome Task Manager (SHIFT+ESPACE) shows that "On device" IA is taking 300% of the CPU (laptop with only low-perf Intel integrated GPU). I can barely type text in an input box: 1 second delay after each keypress.

Disabling the option "On device AI" in the same way than on OP's screenshot doesn't solve this issue: this "On device" process still comes back again and again and I have to kill it manually.

Did someone experience the same?

g0ld3nrati0 |next |previous [-]

you can disable the AI crap in chrome/chromium by setting policy file.

(Linux)

Chrome: `/etc/opt/chrome/policies/managed/disable_ai.json`

Chromium: `/etc/chromium/policies/managed/disable_ai.json`

```

{

  "GenAiDefaultSettings": 2,

  "AIModeSettings": 1,

  "GeminiSettings": 1,

  "GenAILocalFoundationalModelSettings": 1
}

```

edoceo |next |previous [-]

Every app and site I use that has AI integration is slower (Chrome, VSCode, the keyboard on my Android, Bank-Apps). And routing a bunch of stuff into their sites new chat feature which is so buggy that what should be trivial tasks take much longer.

Fast used to be a feature.

I thinking this is just a wave of hot-patch-slop that will pull back soon-ish, if the feedback loop works. Many times the folk making these decisions are so far removed from customer complaints, the there is any complaint (because many users don't bother)

ImJasonH |root |parent |next [-]

I'm old enough to remember a commercial for Chrome that measured a page render against a potato cannon: https://www.youtube.com/watch?v=EYmjoW4vIX8

egnehots |root |parent |next |previous [-]

there was a time where it used to be the defining feature of chrome.

chrome used to be the simplest browser, with a minimal interface that was lean and fast...

SoftTalker |root |parent |next [-]

Google also used to de-rank web pages that were too slow.

chili6426 |root |parent |next |previous [-]

It's hard to believe that Chrome was the obvious choice for power users back then. I miss the blue title bar

eastbound |root |parent |next |previous [-]

That was when user experience was the defining feature of apps.

Ungh |root |parent |previous [-]

Now it's IE6 on cocaine.

giancarlostoro |root |parent [-]

I've always said Chrome became the new IE, especially when you consider that Google and some web devs build sites that only work in Chrome, even though Firefox can run them, I've seen too many sites tell me I should be on Chrome instead, giving me flashbacks to IE in the 2000s...

afavour |root |parent [-]

Chrome moves too fast to be the new IE. The entire web dev industry was frozen in ember accommodating IE6 for years. It was excruciating.

I’m no fan of a Google monopoly but I still prefer where we are today to those days.

giancarlostoro |root |parent [-]

Doesn’t matter if there’s websites that won’t let you in without it, mind you, spoofing Firefox as Chrome lets me through.

SoftTalker |root |parent |next [-]

Since Firefox ~160, Teams has become unusably unstable. "Gah, your tab has crashed" used to be common on startup but after a reload it would be OK. Now it crashes consistently within seconds/minutes.

I have resorted to running Chromium running for Teams, but that's all I use it for. It's the only thing that doesn't work for me in Firefox.

afavour |root |parent |previous [-]

Even that… I use Safari almost exclusively and I can’t remember the last time I’ve seen a prompt like that. It’s way, way less common than the IE6 days.

SoftTalker |root |parent [-]

You really can't get away with not supporting Safari unless you want to write off the the entire iOS user base.

jeffbee |root |parent |previous [-]

Chrome is obscenely fast and it has never been faster. The only thing that can touch it is Safari, a browser that co-evolves with its own hardware platform. Blink and V8 have closed what should have been an unbridgeable performance gap with Safari, and the third place browser isn't in the same galaxy as the top two.

0c3ca83 |next |previous [-]

https://ungoogled-software.github.io/

It doesn't have the AI features, which improves the product quite a bit.

cadamsdotcom |next |previous [-]

Pro tip

You can disable Chrome AI features forever, by switching to Firefox!

londons_explore |next |previous [-]

Chromes mostly open source...

Point to the specific AI features which are wasting bandwidth and quantify how much.

patch_v1 |root |parent [-]

The obvious candidate is the on-device Gemini Nano model behind Chrome's built-in AI APIs. It's a few GB, and you can see its state under chrome://on-device-internals. Chrome's docs say it removes the model again when free disk space drops below a threshold, and downloads it later when space is back. A machine sitting near that line could plausibly churn through the same download repeatedly, which would get you to large monthly numbers without any single feature looking huge.

SlightlyLeftPad |next |previous [-]

I wonder if this ties into a strategy of selling their 3gig google fiber plans.

rdevilla |next |previous [-]

[dead]

leecommamichael |previous [-]

Tangentially; why isn't the technical crowd (who uses Chrome) using Chromium by now? Are you? I switched a while ago and am pleased.