One additional thing to track: reloading the page using a different method other than the "Reload" button on the "Sad Tab" (which we already track as part of the Tabs.SadTab histograms). 

sdy@ - do you have time to work on these additional metrics?

Also - what about shut downs and restarts of other machines/devices?

yyushkina@ - Good point, other ways of reloading definitely seems worth tracking.

I won't have time soon. I can get to them on my back burner, or we could find someone else to work on them, or plan for me to add them next quarter.

I don't think there's precedent to track leaving a sad tab by restarting/shutting down a computer other than a Chromebook. shrike@, any thoughts?

If you can find a little time maybe at the beginning of Q4 for this that would be good.

I'm not sure what tracking the leaving of a sad tab via a restart or reboot would mean. If I get a sad tab page and reload it or type a new URL into the Omnibox I am explicitly taking action to exit the sad tab state. If I have a sad tab and I restart Chrome or reboot my computer, it's not necessarily true that I am taking that action to exit the sad tab.

+1 on beginning of Q4 for this work if you can.

With respect to restarting Chrome or rebooting computer/mobile device, they are suggested "last resort" actions for users experiencing sad tabs. IMO it's not unreasonable to assume that some portion of Chrome restarts or reboots of computer/device immediately after experiencing a sad tab are in response to the sad tab but I'm open to being overruled on this one.

I didn't know they are told about these as a last resort. You are right that it's reasonable that those actions might then occur after a sad tab.

Sounds good.

Hey Sidney, wanted to check in with you on whether you're still able to work on adding additional metrics to the sad tab.

Thanks for reminding me. I don't think I have time, unless shrike@ wants me on it, especially since this isn't Mac-specific. For now, I'll make this bug available.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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