When closing the app, the proxy which was created for the live capture, is not removed. Fiddler Classic would remove the proxy on close.
We got your email, thanks for the feedback Troy.
i sent an email but it looks like it may not have gone through. let me know and i can upload the files if i need to.
Thanks for confirming that you are not observing this issue for now, but feel free to drop in a comment or share your logs if you see this issue again.
"If you could allow us to change the font that would help"
Do you mean to provide a setting to change the font size, or both font type and size? It will also be great if you can tell us your screen resolution and better yet post a screenshot on how Fiddler Everywhere looks on your computer.
this seems to be cleared up for now. I think there was one time it crashed and that may have caused it.
Another time i was using Classic and FE at the same time to compare them. So i will keep an eye out for what might cause the situation.
FWIW, i like the font in Classic much better. I like lots of data on the screen and it just seems that FE doesn't make good use of screen real-estate. If you could allow us to change the font that would help
Thanks for the details.
I can confirm that we are observing this issue sometimes, we are working on improving the cleanup process post app shutdown to make sure the proxy settings are cleared.
It will be great if you can share your application logs for us to analyze, you can find them in this location:
Mac: ~/Library/Application Support/Fiddler Everywhere/Logs
Win: %AppData%\Fiddler Everywhere\Logs\
Also can you please tell us if you are on Mac or Windows.
This happens when i just open the app and then close it. When opening, since it goes right into live capture, it creates the proxy. Then when i close it, i notice that the proxy is not removed and therefore other apps begin breaking. So i start FidEv and stop capture and then close again and it fixes it.
We have seen issues with clearing proxy when Fiddler application closes because of process crash, and we are currently working on improving these scenarios.
But, can you please give us more details if this is consistently reproducible or happens infrequently?