Deadlock when close hub frame

[3x3x3]

Hello there.

I runned the debug version in VisualStudio 2003 debugger.
I connected to a hub, then closed the HubFrame, DC++ deadlock.
I am using 0.403 without any change, compiled with WTL7.1 + stlport4.6.2 got from here:

http://sourceforge.net/project/showfile ... e_id=32827

After pause the program and check stacktrace, I found the WTL::CButton.GetCheck() didn't return.
Please see the screenshot for more information.

http://www.aloofhosting.com/3x3x3/

Any help is appreciated.

[TheParanoidOne]

Image not working.

[Guitarm]

Strange, I've compiled and run 0.403 in both debug and release modes and I haven't seen this error. Are you sure you have included stlport and wtl the right way ?

Regards

[3x3x3]

thanks for reply.

I tested this with DC++ release version, and got the same result.
How to test:
1) connect to a laggy hub with 3000+ users
2) once you receive user list, close the hub window at once.

retry if no freeze.

[GargoyleMT]

Closing a hub window while the user list is being loaded is a known issue. Of course you see it most on large hubs. If you want to take a look at it and work up a fix, that would be appreciated.


I've seen deadlocks, but only in debug mode on cvs derived clients - BCDC. In my case, disabling the hub flashing (seems to have) fixed it.

[JohnSmith]

Hello there.
Please see the screenshot for more information.
http://www.aloofhosting.com/3x3x3/

OT: What is the font you used in Editor?

[Big Muscle]

Deadlock is caused by function HubFrame::getUserInfo();

Code: Select all

   bool getUserInfo() { return ctrlShowUsers.GetCheck() == BST_CHECKED; }

I've just replaced its content with

Code: Select all

   bool getUserInfo() { return ShowUserList; }

and no deadlocks now )