Blink>Loader triager here.

Couldn't reproduced 59.0.3071.115 and 61.0.3160.0 on Windows 7.

Does this reproduce reliably in your environment?
How about with different versions (e.g. M-60, M-61) or with clean profiles?

Are you by any chance running with the history-entry-requires-user-gesture flag enabled? I saw a similar issue that in M59 that I believe was related to that flag, but M60 narrowed that flag's behavior enough that I haven't seen it since.

#2 - I did not check other versions and it does not happen all of the time, only sometimes.
#3 - I did not enable anything related, but a field trial might have bit me here. :(
You and your shiney experiments... :P
I will check that machine on Sunday. How do I know whether it is enabled by a field trial?

#3 - "New history entries require a user gesture." is not enabled by me.

My variations from about:version -
98ee9f3e-98ee9f3e
ca7e5485-3f4a17df
241fff6c-4eda1c57
3095aa95-3f4a17df
6c43306f-ca7d8d80
7c1bc906-f55a7974
1c752ce9-33c3eba5
d43bf3e5-ad6ab04f
ba3f87da-b4a760c3
cf558fa6-48a16532
5ca89f9-ca7d8d80
f3499283-7711d854
9e201a2b-1359b0af
9bd94ed7-b1c9f6b0
9773d3bd-ca7d8d80
b22b3d54-1c15b2e9
2e109477-f3b42e62
99144bc3-132064d0
9e5c75f1-51efb9f9
f79cb77b-3d47f4f4
b7786474-d93a0620
9591f600-d93a0620
27219e67-b2047178
23a898eb-e0e2610f
4ea303a6-225f7d4f
7aa46da5-669a04e0
64224f74-5087fa4a
56302f8c-ca7d8d80
de03e059-e65e20f2
cac0a91c-3f4a17df
2697ea25-ca7d8d80
b2f0086-93053e47
6844d8aa-669a04e0
494d8760-3d47f4f4
f47ae82a-86f22ee5
3ac60855-486e2a9c
f296190c-a2200d3b
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-d7f6b13c
e2b18481-7158671e
e7e71889-4ad60575
288c530e-3fc362e4
61b920c1-ca7d8d80
828a5926-ca7d8d80

I can still reproduce in Chrome 60. No special steps. I go to some message, go to the inbox, go to another message and try to go back to the previous message by clicking back twice and it reloads GMail.
It does not always happen, just like before.

Could you try it on other browsers? It might be an issue of gmail side.

It might be a local issue, because I only experience it on one machine (Windows 7 Enterprise). But I am not sure any extension causes it... I will recheck my extensions. The problem is that it is not consistent.

Thank you for providing more feedback. Adding requester "ksakamoto@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

@phistuck-- Could you please provide us update on this issue , if you can still able to reproduce the issue in latest stable .

Thanks!

It happened to me once (a few days ago) on a different machine with Chrome 61, so, yes, unfortunately, it still reproduces and still intermittent. :(

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Tested on latest Chrome #61.0.3163.100 and Canary #63.0.3235.0 on Windows 7 and Windows 10 and not able to reproduce the issue. Could someone from dev team please look into the issue.

Thanks!

Still wondering if this is gmail side issue. Phistuck, have you had chance to try on other browsers?

#14 - I will have to use that other browser for a while in order to reproduce and frankly, I am dreading experiencing the web on other browsers. So, no. :(

#14 - I am willing to keep my Developer Tools open for GMail, but that will not help because setting a break point on beforeunload or unload or something does not show a stack trace and you cannot break on navigations otherwise and see a stack trace.

ksakamoto@,

Could you please respond to this issue as per C#16.
Thanks..!

Yeah I don't think keep devtools open will help.

Let me set Pri-3 until we have a reliable repro case.

Loading triage: set Needs-Feedback to gather information to reproduce the issue in a reliable way.

It just happened again. It is sporadic, I am not sure how to reproduce, but it definitely happens.

Thank you for providing more feedback. Adding requester "toyoshim@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

wasn't decisive comment. set the same label again.

phistuck@, can you reproduce this without installing any Chrome Extension? It has enough abilities to cause this kind of problems.

#22 - it would be pretty hard for me to manage without them... I will see what I can do (that means I have to open another instance of Chrome with only GMail, which sucks in terms of memory usage).

Thank you for providing more feedback. Adding requester "toyoshim@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

I started using GMail in a separate instance with a separate user-data-dir and --disable-extensions (because this is an enterprise computer that automatically installs some extensions. Surprisingly, the flag worked and those extensions were not installed - a bug? :S).
I will report back in about a month or earlier, because like I mentioned, when it happened, it happened sporadically and very infrequently (I think about ten times in a few months).

Intentionally not setting Needs-Feedback because it has a short deadline. Setting the Next Action date instead.

The NextAction date has arrived: 2018-01-11

It has not happened again ever since I started using a new clean profile for GMail, so I guess it is one of my extensions (or luck). I suspect Google Dictionary...

Thanks for the update.

Let's close this issue as it's not reproducible.

I'm now installing the Google Dictionary. It just looks useful, and I can share information if I also can reproduce the issue with this Extension.

#30 - :)

I just installed it on that new profile and used it to describe some word (and clicked on "more >>"), went to a few messages and clicked on the back button of the browser and voila - it happened.
So I am 99.9% sure Google Dictionary is the culprit. Can you file an internal issue with that team (or find the code the fix it? ;))?

Thank you.

Thank you for your confirmation.
I filed an internal bug and assigned it to the team.
Internal link to the bug is b/74510001, the link works only for Googlers.

I looked at the code of the extension a bit (minified, but I looked for web platform APIs or Chrome extension APIs) and could not find anything that would do this.
How would you even cause this to happen intentionally without the obvious location API (I only found getters)?

I still suspect a browser bug, really.