[Expired for DC++ because there has been no activity for 60 days.]
** Changed in: dcplusplus
Status: Incomplete => Expired
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1154143
Title:
Random freeze DC++ 0.811
Status in DC++:
Expired
Bug description:
Converted from Question #223910
So I achieved a frozen DC++ ( http://i.imgur.com/fZMYcrT.png ). But
when I go to SysInternals, none of the threads have 100% CPU usage. In
fact, all threads have no CPU usage (http://i.imgur.com/yybQoVe.png) .
Anyhow being unable to identify the bugged thread, I went ahead and
attached gdb to thread with id _9156_ because it had that weird Start
Address "...!TpCalbackIndependent...". And obtained a stacktrace
(http://sprunge.us/VLSW).
Was this process correct? Next time I encounter such a problem, how
can improve the collected information for a bug report? (Note- I'm not
filing a bug report yet because I'm not even sure if I have the
correct inormation for it yet.)
Symptom: DC++ stops working after a random time. Sometimes just a few minutes
after start, or sometimes many hours.
Details: DC++, version 0.811, Windows 7, 64-bit
Here is trace for all the threads: http://sprunge.us/YTjK
ProcessExplorer: http://i.imgur.com/CKoPihz.png
To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1154143/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~linuxdcpp-team
Post to : linuxdcpp-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linuxdcpp-team
More help : https://help.launchpad.net/ListHelp
