hi,
i would like some feedback on how to locate issues related to a freezing client.
my (lastest) client 3.2.3 runs in a hyperV with win7/2GB/2 vir cores.
It ran fine until i recently added/manipulated some torrents with *alot* of small files
after some time i noticed the view became unresponsive.
disk/memory access was fine while total cpu was at 70% which is alot (normally <20%) . the torrent related data is on a separate disk
i could not do anything like switching to exec log to view data
a suspend /restart of the client did not make any difference.
finally i killed the client and after restart launched verification of the running torrents because i got missing file errors (which is kinda strange)
some things i could have checked at that time but failed to do :
- checking if there was any activity/transfer going on (with tools like procmon and firewall data transfer logs)
i doubt the exec log by itself is/would be usefull in any way (this is a memory only log i think as i could not find a physical connection yet).
basically my question is : is there some type of debug (aka extensive) logging possible that would be usefull for reporting a (possible) bug ?
tnx.
update 2 days later:
/ closed.
replaced by a new post with more details in the improvement request section.
req info related to freezing of qbit client (closed)
req info related to freezing of qbit client (closed)
Last edited by nugget on Sat Aug 29, 2015 10:25 am, edited 1 time in total.