UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Setup a server (e.g. localhost) and update your /etc/hosts to make a normal domain (like subdomain.domain.com) pointing to that server
2. Update your /etc/hosts file
3. Notice that Chromium still directs me to the original server (not overriden by /etc/hosts)
4. Disable prediction service to load pages more quickly
4. chrome://net-internals/#dns click clear host cache
5. run devtools with cache disabled
6. hard reload with Ctrl + F5
7. Restart Chromium
8. Notice that Chromium STILL points to the original server, ignoring completely recent modifications to /etc/hosts
9. If I start another profile, it works. 

What is the expected behavior?
See steps to reproduce

What went wrong?
I'm developing a frontend application and I must use the same domain for development as for production. Hence I use /etc/hosts file to point my domain (actually its a subdomain.domain.com if it matters) to localhost when I need to develop it. However Chromium has trouble noticing that change in /etc/hosts. Just nothing works, I tried everything. The only way is to either way unpredictably long time or create a new browser profile.

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 62
Flash Version: