Capturing traffic stops when dragging the "Any process" target to Chrome

2 posts, 0 answers
  1. Andres
    Andres avatar
    1 posts
    Member since:
    Apr 2019

    Posted 04 Apr Link to this post

    When I drag the target next to "Any Process" onto a Chrome window, to capture traffic only from Chrome, no traffic is captured. But without specifically targeting Chrome the traffic from Chrome shows up in Fiddler. Same problem appears with Edge browser, but with IE it works as expected. I have no active filters or specific rules. Also tested it on multiple PCs and got the same results. Any ideas what's causing this?

  2. Simeon
    Admin
    Simeon avatar
    231 posts

    Posted 09 Apr Link to this post

    Hello Andres,

    Thank you for addressing this issue. As far as I know, the Chrome and the Edge browsers are using multi-process architecture. This means that it is possible that the process who is using the network resources is different from the main window. Hence, when you place a filter in Fiddler to show only traffic from the process of the main window of the internet browser, you are hiding the traffic from the process which is using the network resources.

    In order for Fiddler to adapt to the multi-process architecture of the browsers, we will have to research if there is a deterministic way to find from which process(es) the browser is using the network resources.

    Meanwhile, you could use a different technique to capture traffic only from the Chrome or Edge browsers. When the first request/response goes through Fiddler you could right-click on the session in the sessions list view on the left side and click on the Filter Now > Show Only Process= ProcessID context menu.

    Later, when you want to remove the filter, just right-click on the Hide Process!= ProcessID label below the QuickExec command line.

    Regards,
    Simeon
    Progress Telerik
    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? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top