[Pidgin] #13252: Pidgin main thread hangs after starting application and on initial call to libpurple.dll!wpurple_close on 2.7.9.0 (Win)

[Pidgin]

#13252: Pidgin main thread hangs after starting application and on initial call to
libpurple.dll!wpurple_close on 2.7.9.0 (Win)
------------------------+---------------------------------------------------
 Reporter:  fastCode04  |        Owner:           
     Type:  defect      |       Status:  new      
Milestone:              |    Component:  libpurple
  Version:  2.7.9       |   Resolution:           
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by fastCode04):

 And here its is, a full call stack (Process Hacker):

 0x828e6eec, ntkrnlpa.exe!KiDeliverApc+0xce

 0x828df375, ntkrnlpa.exe!KiSwapThread+0x472

 0x8287af28, ntkrnlpa.exe!KeWaitForSingleObject+0x492

 0x915875e4, afd.sys!AfdCleanupCore+0x6b3

 0x9158773e, afd.sys!AfdDispatch+0x11c

 0x828779c6, ntkrnlpa.exe!IofCallDriver+0x63

 0x82a73818, ntkrnlpa.exe!IopCloseFile+0x387

 0x82a6d6b7, ntkrnlpa.exe!ObpDecrementHandleCount+0x146

 0x82a6d45a, ntkrnlpa.exe!ObpCloseHandleTableEntry+0x234

 0x82a6d16d, ntkrnlpa.exe!ObpCloseHandle+0x73

 0x82a6d851, ntkrnlpa.exe!NtClose+0x20

 0x8287dc7a, ntkrnlpa.exe!KiFastCallEntry+0x12a

 0x77885e74, ntdll.dll!KiFastSystemCallRet

 0x77884320, ntdll.dll!NtClose+0xc

 0x1001cd48, Engine.dll+0x1cd48

 0x7545260d, MSWSOCK.dll!SockCloseSocket+0x225

 0x754526c4, MSWSOCK.dll!WSPCloseSocket+0xb2

 0x2531bf3, RSLSP.dll!AuthenticateLicense+0xe773

 0x67d1db51, libpurple.dll!wpurple_close+0x21

 Call Stack (WindDBG):
  # ChildEBP RetAddr  Args to Child
 00 0022ecfc 77884320 1001cd48 000001e4 0022ed74 ntdll!KiFastSystemCallRet
 (FPO: [0,0,0])

 01 0022ed00 1001cd48 000001e4 0022ed74 7545260d ntdll!NtClose+0xc (FPO:
 [1,0,0])

 WARNING: Stack unwind information not available. Following frames may be
 wrong.

 02 0022ed0c 7545260d 000001e4 07763120 05a103b0 guard32+0x1cd48

 03 0022ed74 754526c4 04640908 05a103b0 03c207d8
 MSWSOCK!SockCloseSocket+0x225 (FPO: [Non-Fpo])

 04 0022ed8c 02511bf3 000001e4 0022ee4c 05a103b0
 MSWSOCK!WSPCloseSocket+0xb2 (FPO: [Non-Fpo])

 05 0022ee50 67d1db51 000001f0 05a103b0 0022ee80
 RSLSP!AuthenticateLicense+0xe773

 06 00000000 00000000 00000000 00000000 00000000
 libpurple!wpurple_close+0x21

 Both aquired from the same process and there is one difference in the
 stack so far: The guard32.dll is a Comodo Antivirus Component, i checked
 now, but i dont think that this is the fault, there was never a problem
 with comodo on the pidgin process.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/13252#comment:5>
Pidgin <http://pidgin.im>
Pidgin