Closing DC++ 0.75 on XP SP2 x64

Asked by zZz

When the DC++ application is closed on Windows XP SP2 x64 bit version , the process still remains in the memory (I Have checked this with task manager and on 4 different systems) .

This also might interfere with kaspersky firewalls in some cases (downloads are slow)

Question information

Language:
English Edit question
Status:
Solved
For:
DC++ Edit question
Assignee:
No assignee Edit question
Solved by:
zZz
Solved:
Last query:
Last reply:

This question was originally filed as bug #390219.

Revision history for this message
zZz (morosanu-robert-bc) said :
#1
Revision history for this message
eMTee (realprogger) said :
#2

What happens to other p2p software? Do they slow / remain in the memory as well? Have you tried with the firewall disabled / unistalled / properly configured? Do you use the latest version of the firewall?

Revision history for this message
zZz (morosanu-robert-bc) said :
#3

Other P2P software are not affected by this issue , I have tested , but I prefer DC++ because it's much simple than other apps ;
Disabeling the firewall has no effect as I also tested with NO firewall - and an installed firewall is properly configured .
I am using the latest version of the firewall .

Revision history for this message
eMTee (realprogger) said :
#4

Afaik none of the developers/contributors use XP x64 so I'd say that DC++ (0.75) is not tested officially in that OS.
What I can suggest to try :

- Wait some time and check if the process ends after several minutes (up to 10-20 mins).
- Make sure that DC++ is not hashing (a large file) when you close it (If so, the process wont end until it finishes with the current file - this will be fixed in the next version).
- Try to disable / uninstall other possibly incompatible applications. Focus on those which are monitoring/indexing the file system and network traffic.
- Check if you have updated x64 drivers in the >OEM< vendors of your hardware. Focus on the LAN and the storage/chipset drivers.

Revision history for this message
zZz (morosanu-robert-bc) said :
#5

- Wait some time : I have waited around 1 Hour and 15 Minutes and it's still there , so I guess it's pretty obvious .
- It is currently not hashing a big file or hasn't finished hashing (share)
- No incompatible software installed that could might interact with DC++
- All x64 OS and Motherboard + Hardware Drivers are up to date plus Windows is Full Updated

I'm looking forward to see the next version , It's really frustrating that this process remains active even if the application is closed .

Revision history for this message
poy (poy) said :
#6

turning into a question until the actual cause is found.

Revision history for this message
poy (poy) said :
#7

what do you mean with "4 different systems"? all 4 are XP x64?

here is a version that i build that runs natively on x64 systems; compiled with the MS compiler: <http://www.sendspace.com/file/51t4a1>. try it and see if it helps.

it looks like the app isn't exactly hung, but more like caught in an infinite loop since the CPU usage is so high. in my experience this has most often been caused by third party applications interfering with DC++ - you should check again.

Revision history for this message
zZz (morosanu-robert-bc) said :
#8

Yes , I was refering to 4 different computers that were using the same Windows XP SP2 x64

EDIT !

All seems Fine For the x64 Version you supplied it .

Seems fine now , and process is closing properly .

Thank you very much !