Fiddler not exiting after update.

4 posts, 0 answers
  1. Cliff
    Cliff avatar
    2 posts
    Member since:
    Feb 2017

    Posted 22 Feb 2017 Link to this post

    Not sure from when, Fiddler simply won't terminate after clicking the close button. Updated to the latest version v4.6.20171.9220, the issue is still there.

    My OS is Win7 Ent SP1.

     

    Call stack of the hanging thread.

    ==============================================

    OS Thread Id: 0x6a30 (7)
            Child SP               IP Call Site
    000000001ee9e848 0000000076dcc0ea [HelperMethodFrame_1OBJ: 000000001ee9e848] System.Threading.WaitHandle.WaitOneNative(System.Runtime.InteropServices.SafeHandle, UInt32, Boolean, Boolean)
    000000001ee9e970 000007fee0d1a0d1 *** WARNING: Unable to verify checksum for C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\fa8eef6f6cb67c660d71e15c5cad71b5\mscorlib.ni.dll
    System.Threading.WaitHandle.InternalWaitOne(System.Runtime.InteropServices.SafeHandle, Int64, Boolean, Boolean)
    000000001ee9e9a0 000007fee0d1a0a1 System.Threading.WaitHandle.WaitOne(Int32, Boolean)
    000000001ee9e9e0 000007fed62da532 *** WARNING: Unable to verify checksum for C:\Windows\assembly\NativeImages_v4.0.30319_64\Telerik.Analytics\8d921e35a226a0a0c0cdc9bacfd59599\Telerik.Analytics.ni.dll
    *** ERROR: Module load completed but symbols could not be loaded for C:\Windows\assembly\NativeImages_v4.0.30319_64\Telerik.Analytics\8d921e35a226a0a0c0cdc9bacfd59599\Telerik.Analytics.ni.dll
    Telerik.Analytics.Utility.WaitHandleUtil.WaitOne(System.Threading.WaitHandle, System.TimeSpan)
    000000001ee9ea10 000007fed62dccb7 Telerik.Analytics.Network.ServiceRequest.SendRequest(System.TimeSpan)
    000000001ee9ea70 000007fed62da979 Telerik.Analytics.Core.Submitter.Submit(Telerik.Analytics.MonitorSettings, System.TimeSpan, System.String, System.String)
    000000001ee9eb80 000007fed62d8a86 Telerik.Analytics.Core.Dispatcher.b__2()
    000000001ee9ec80 000007fed62cf4e9 Telerik.Analytics.Utility.CodeUtil.SafeAction(Action)
    000000001ee9ecc0 000007fed62d8187 Telerik.Analytics.Core.Dispatcher.GetAndSendNextPacket(Telerik.Analytics.Core.Submitter, System.TimeSpan, System.String)
    000000001ee9ede0 000007fed62d876c Telerik.Analytics.Core.Dispatcher.b__1()
    000000001ee9ee30 000007fed62cf4e9 Telerik.Analytics.Utility.CodeUtil.SafeAction(Action)
    000000001ee9ee70 000007fed62d8104 Telerik.Analytics.Core.Dispatcher.IncomingDataLoop()
    000000001ee9eeb0 000007fee0d22490 System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    000000001ee9ef80 000007fee0d22327 System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    000000001ee9efb0 000007fee0d31a50 System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
    000000001ee9eff0 000007fee0d31f70 System.Threading.ThreadPoolWorkQueue.Dispatch()
    000000001ee9f518 000007fee21d3753 [DebuggerU2MCatchHandlerFrame: 000000001ee9f518]

  2. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    549 posts

    Posted 24 Feb 2017 Link to this post

    Hi,

    That is a weird one. Does everything else work normally? If you stop capturing before close does something change? What about viewer mode? Does it exhibit the same behavior?

    Regards,
    Tsviatko Yovtchev
    Telerik by Progress
    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
  3. Cliff
    Cliff avatar
    2 posts
    Member since:
    Feb 2017

    Posted 06 Mar 2017 in reply to Tsviatko Yovtchev Link to this post

    Sorry for the delay. Everything else works just fine except that it looks a little bit slower but no big difference.

    It would hang there even if I stop capturing or in viewer mode. If I close the window, the window do get closed but the process remains for ever. I've kill the process manually.

    Thanks.

  4. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    549 posts

    Posted 08 Mar 2017 Link to this post

    Hi,

    This issue is caused by Fiddler Script Editor and happens only in pre-2017 versions of Fiddler. The 2017 version should not exhibit this problem. A clean install including removing any old FSE installs is needed though. Please, note that 2017 version of Fiddler include FSE and it is not available as a separate add on any more. Please, do not install any old versions of FSE add on on top of 2017 Fiddler.

    Regards,
    Tsviatko Yovtchev
    Telerik by Progress
    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