[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:  pending  
Milestone:              |    Component:  libpurple
  Version:  2.7.9       |   Resolution:           
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by fastCode04):

  * status:  pending => new


Comment:

 Replying to [comment:3 deryni]:
 > A hang in closesocket doesn't immediately sound like something that
 pidgin can be causing to me.
 >
 > Are you running any firewall/anti-virus/etc. software?

 You are right, it doesnt mean that it is caused by pidgin, but maybe some
 unexpected data(structure) flowing through the socked on the calls make
 some lower call to a function on the stack (kernel or user land) do some
 unexpected wait or lock/block somewhere. In that case this isnt a fault of
 pidgin for sure, but maybe it can be intercepted by some higher library or
 pidgin can check to make sure it wont happen. It is (for sure!) not the
 task to eliminate others bugs, but everything is asumption here at first,
 any possible cause! There can be many reasons. It would be great if i had
 the call stack saved somwhere,... :-( It was a deep call to a kernel APC
 call and before that some wait functions, but this for sure is nothing
 that helps here, except something is waiting for something,...i really
 forget the calls stack, the most important here!

 Yes, i do run a fw (Windows Vista FW with fully non blocking rules for
 Pidgin) and av (comodo fully exlcuding Pidgin process and files with
 rules, only the AV, no sandboxing or api-hooking/defense mechansim, all
 disabled), in fact there was never a problem with that, all works fine.

 I did look into the system logs and they only report "Application does not
 respond", too bad no more info except this (old record but same problem):

 Protokollname: Application
 Quelle:        Application Hang
 Datum:         18.01.2011 02:37:20
 Ereignis-ID:   1002
 Aufgabenkategorie:(101)
 Ebene:         Fehler
 Schlüsselwörter:Klassisch
 Benutzer:      Nicht zutreffend
 Computer:      somesystem
 Beschreibung:
 Programm pidgin.exe, Version 2.7.9.0 arbeitet nicht mehr mit Windows
 zusammen und wurde beendet. Überprüfen Sie den Problemverlauf im Applet
 "Lösungen für Probleme" in der Systemsteuerung, um nach weiteren
 Informationen über das Problem zu suchen. Prozess-ID: 1a98 Anfangszeit:
 01cbb6ae1c1c42d0 Zeitpunkt der Beendigung: 60000

 It says that the application does not work anymore with windows and has
 been terminated, but the process in fact is still running, as described
 before. It looked like some zombie process but it isnt, at least to me at
 first.

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