hi, thanks for reporting this. Can you please file a feedback report from within Chrome? Sending the feedback report from Chrome attaches metrics to the report which makes it possible for us to debug the issue. Instructions for sending the feedback report:
https://support.google.com/chrome/answer/95315?co=GENIE.Platform%3DDesktop&hl=en

Can anyone help me with this?

Am I the only one who is reporting this problem?

Thank you for providing more feedback. Adding the requester to the cc list.

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

I did a Powerwash and the Data Saver extension resumed working.

But next day Data Saver quit again.

Did another Powerwash and Data Saver okay again.

Looks like this might become a daily practice.

Hi OP, Can you explain how you determine if the data saver is working or not? 

Note that the data saver currently proxies only the http webpages (and not https). So, the observed savings may vary from day-to-day based on the type of websites browsed by the user. If the user browses mostly http websites, then the savings would be higher.

Clicking on the Data Saver icon shows Data Usage = 0 bytes. 

Clicking on Details also shows 0 bytes used.

Thanks.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Hi OP,

Have you enabled the data saver using the data saver extension? You can verify that by looking at the checkbox in the extension interface.

There is a known bug on desktop where if the data saver is not enabled, then the extension does not show data usage count properly. However, if the data saver is enabled (the checkbox is enabled), then the data usage should not have been 0.

Thanks, yes, data saver is enabled.

If data saver is enabled, then this seems like a different bug. Assigning to rajendrant@ to take a look at this.

I am able to reproduce this issue in chromeos.
I will rootcause and fix this.

I suspect CDUA is getting disabled via this code:
https://cs.chromium.org/chromium/src/components/data_reduction_proxy/core/browser/data_reduction_proxy_io_data.cc?rcl=752dbfde3778415a318dec924989a3a9c5170eb6&l=432

I am delaying working on this bug, since CDUA migration work in happening.

Tarun, Raj suspects your code. Can you confirm?

I am not sure why this has RVG label given that the bug was filed by an outsider?

I am going to remove RVG since there does not seem anything google-sensitive here.

Re #12: rajendrant: Can you list the repro steps here. Thanks.

Assigning back to Raj to get the details on the repro. Raj, can you also summarize your findings from the feedback report filed by the OP? Thanks!

Repro is to reboot with DRP enabled.
When chromeos boots to login screen, DRP is not enabled (profile is not loaded?)
So CDUA gets disabled.
Once the user logs in DRP is enabled. But CDUA is left disabled.

As discussed with Tarun, we did not want to enable CDUA at this point (from a previously disabled state) since it could expect UserData in requests and behave in a weird manner.

I also saw that DataReductionProxy.StartupState is logged two times. Once with state disabled (at login screen), and once as enabled (when user logs in).

https://cs.chromium.org/chromium/src/components/data_reduction_proxy/core/browser/data_reduction_proxy_settings.cc?rcl=f9b9a0c8e47d63178ad3262ca3dc79efef1f3080&l=291

We also discussed if this issue should be fixed now, since CDUA migration is happening.

We disable CDUA on ChromeOS when data saver is disabled. This check happens at the time of browser startup. If later, the user enables data saver in the session, then CDUA does not report anything. Chrome has to be restarted before CDUA starts working again.
This was a bandaid solution for all the crashes happening due to CDUA on desktop.

ChromeOS makes this situation complicated as the decision to enable CDUA is decided at the time of machine startup. However, DRP is enabled after the user logs in. May be we can check for the DRP state in the main profile on Chrome OS.

Any progress on this issue?

thanks,

Don

I'm curious what the status of this issue is. Has a solution ben found?

thanks,

Don

Hi Don,

Yes. We have committed the fix.
I have verified the issue is fixed in Chrome OS.
We will be rolling out the fix in M69, in a few weeks.

Thanks

Thanks!

I have M69 now but data saver still doesn't work. Any suggestions?

thanks,

Don

Fixed and fully launched now.

Thank you Rajendrant! It's working for me again!

I am seeing 13.6% savings this morning.

thanks again,

Don