Chrome uses multiple processes to render the UI and separate background processes to issue network requests - make sure that the correct process is selected among all Chrome-related processes in the filter.
Another option is to uncheck Tools -> Options -> Connections -> Act as system proxy on startup, and then Start Chrome with manually specified proxy settings, pointing to the port on which Fiddler is listening:
This way the only captured traffic will be from this instance of Chrome.
If I am missing something, could you please provide specific steps to reproduce the issue?
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items