I'm using fiddler2 to substitute certain requests to the webserver. Those requests occur about 10 per second. Fiddler performance is falling down with time, about 1 hour of work and then it starts lagging on proxing response. Also memory usage grows. This could be solved with restart of fiddler.
I suspect this is caused by growing log size and some scanning operation on whole request log, which runs on each request.
Is there any way to configure fiddler to avoid such leaks? Maybe some way to reset it's memory or logging data by fiddler rules, or set limit to its size?
For scenarios like this, you want to ensure that Fiddler is dropping traffic as soon as it's done with it. The simplest way to do that is to set the Keep only dropdown on Fiddler's toolbar so that it discards Sessions as they are completed.
See http://fiddler2.com/documentation/Troubleshoot-Fiddler/OutOfMemory for other tricks you can use to accommodate large responses, streaming data, etc.