[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):

 Replying to [comment:8 Sebbe]:
 > Replying to [comment:7 fastCode04]:
 > > Replying to [comment:6 Sebbe]:
 > > > This sounds like the issue I'm seeing, as well.
 > >
 > > What exactly do you encounter?
 >
 > After a while, Pidgin hangs, unable to be killed. Attaching a kernel
 debugger gives me that it appears to be stuck, waiting to return from a
 call to kernel mode.
 >
 > I don't recall which kernel call exactly, but it sounds likely to be the
 same thing.

 Can you provide a user->kernel stack, so we can see what exactly stucks.
 In my calltack the final call goes to the windows apc dispatcher
 KiDeliverApc() routine. The calling thread suspends and resumes only after
 KiDeliverApc() returns,...and here it seems that it doesn not return and
 hence the thread cant be killed. The windows apc stuff is pretty
 complicated and party undocumented and so it is really difficult to find
 the real cause for that hang. :-( But as you explain it possibly could be
 the same issue you have...

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