I've been able to make a few screenshots. In the first one (name ending by 81429), you see I've typed "google" and nothing shows up (although network access is perfect, there's no logical reason whatsoever).
 
Ironically, I found out that making the screenshot DOES help once: the second screenshot (81442) shows the results I had right after the screenshot was made. However, after that it remains stuck: in that same screenshot you see I added "test"  to have "google test" as a query, but it's still showing the old result just for "google". New screenshot (81457) and the results are updated but again only once, results for "google test" although I've added "something else". Another screenshot (81503) and you now see the results for "google test something else". Restarted the app and I've got the expected behavior again (but only for a short time). 

Deleted: Screenshot_20170826-081429.png 106 KB

	Screenshot_20170826-081429.png 106 KB View Download

Deleted: Screenshot_20170826-081442.png 139 KB

	Screenshot_20170826-081442.png 139 KB View Download

Deleted: Screenshot_20170826-081457.png 130 KB

	Screenshot_20170826-081457.png 130 KB View Download

Deleted: Screenshot_20170826-081503.png 114 KB

	Screenshot_20170826-081503.png 114 KB View Download

Tested the issue using 61.0.3163.60 on OnePlus 3T 7.1.1 and was unable to reproduce the issue as per the steps mentioned in comment #0. Able to see search suggestions even after browsing for 20 to 30 mnts.

@stevelersberghe: Could you please clear the Cache and browsing data and check if you still face the issue, If so please help us with a screen cast, that would help us in further triaging of the issue.

Thanks!!

Thanks for the quick follow-up.

In the meantime I've totally reinstalled the app but no change, behavior is still there.

Should I still try clearing the app cache and browsing data or has the app reinstall already done that automatically?

When you mention screen cast, do you mean a captured video I record or rather live casting? The former should be doable at some time, the latter would require quite some coordination.

Thank you for providing more feedback. Adding requester "sandeepkumars@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

tedchoc: are you aware of any changes recently to the omnibox or autocomplete system in M61 on Android that may result in the reported behavior (no response at all from the autocomplete system after the app is running for some time).

If it can help to determine the cause, I mention once more that making a screenshot (to illustrate this issue) does reactivate the autocomplete system once. 

@changwan, did the new input mode go into M61?

I'm wondering if you went to chrome://flags and look for "Spannable inline autocomplete" and turned that to "Disabled" does the problem still show up?

If it isn't this input model, then I'm not aware of any other large changes that could have caused this.

reporter, what keyboard app are you using?

 issue 754758  might be related. Reassigning to myself first.

It's SwiftKey. I just disabled the Spannable inline autocomplete in the flags, will keep you updated. Can also try a different keyboard app if that doesn't change anything. 

The spannable inline autocomplete didn't help, issue came back in no time. Reverted to default and using Gboard now,to check if that makes any difference.

stevelersberghe@, just to confirm, did you restart the app after disabling spannable inline autocomplete?

Yes I did, using the button that Chrome immediately shows after changing the setting.

+askatte@ for repro steps
+mpearson@: is this a known issue?

The keyboard did it: since using Gboard, the issue didn't come back so far. Now reverting to SwiftKey (which remains my preferred keyboard by quite some margin, sorry for the Gboard fans here ^^) to see if it comes back.

Do you still see this problem?

Actually not, I'm using SwiftKey again since some time (I actually did a few extra switches between Gboard and SwiftKey since my last message) but couldn't notice any issue since.

Both Chrome Beta and SwiftKey have been updated in the meantime, so I'm not 100% sure what exactly solved it.

Thanks for your assistance in any case!

Ok, thanks for the feedback. Issue 764749 has been fixed, and this sounds like a dup.