Error when saving fiddler trace

2 posts, 0 answers
  1. Eric
    Eric avatar
    1 posts
    Member since:
    May 2014

    Posted 13 Jan 2017 Link to this post

    Awww, Fiddlesticks!
    Fiddler has encountered an unexpected problem. If you believe this is a bug in Fiddler, please copy this message by hitting CTRL+C, and submit a bug report at
    The wait completed due to an abandoned mutex.
    Type: System.Threading.AbandonedMutexException
    Source: mscorlib
       at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
       at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
       at Fiddler.frmViewer.‹•(String[] ˆ•) in c:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 2809
       at Fiddler.frmViewer.‡•(String[] ˆ•) in c:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 2717

    Fiddler v4.6.3.50306 (x64 AMD64) [.NET 4.0.30319.42000 on Microsoft Windows NT 10.0.14393.0]


    What's odd is I don't have a c:\JenkinsHome directory.



  2. Eric
    Eric avatar
    5 posts
    Member since:
    Feb 2012

    Posted 25 Jan 2017 in reply to Eric Link to this post

    The file path shown in the stack trace is a red herring; it has nothing to do with your problem.

    The Telerik team made the ...unusual... decision to both obfuscate the assemblies (so the stack trace is useless) *and* ship the PDB files (so that the filenames on the Telerik build server are shown.

    Can you reproduce this problem? If so, what are the steps?

Back to Top