Last Updated: 18 Jan 2022 06:53 by ADMIN
Created on: 11 Mar 2019 19:31
Type: Bug Report
"Target Any Process" feature no longer working with Chrome

"Target Any Process" feature no longer working with Chrome. It used to work but no longer works specifically with Chrome. Still works with other processes. Capturing still works with Chrome as long as I am not using the "Target Any Process" feature.

Nick Iliev
Posted on: 18 Jan 2022 06:53

Hey everyone,


The latest version of Fiddler Classic now resolves this issue and the option "Target Any Process" is now working with Chromium-based browsers like Chrome, Brave, etc.


Nick Iliev
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Posted on: 26 Aug 2020 18:17
Posted on: 11 Mar 2019 20:25


Chrome recently moved to using a "Network Service" for networking, and that service can run out-of-process to the main browser window (where the networking code used to run). (See chrome://flags/#network-service-in-process in Chrome)

As a consequence, when you drop the dropper icon on the Chrome window, you'll get the process ID of the Chrome UI, but not the process ID of the Chrome Network process (from which the traffic emanates). 

You'll have to use one of the other filtering features to achieve your goal (e.g. capture a request from Chrome, right-click and choose Filter Now > Show only process ...)