RE: Re: Re: TortoiseProc.exe Hangs on Initial startup

m_bBusy is false.

The call stack looks pretty clean:
TortoiseProc.exe!CSVNStatusListCtrl::OnPaint()
mfc100ud.dll!CWnd::OnWndMsg()
mfc100ud.dll!CWnd::WindowProc()
mfc100ud.dll!AfxCallWndProc()
mfc100ud.dll!AfxWndProc()
mfc100ud.dll!AfxWndProcBase()
user32.dll!UserCallWinProcCheckWow()
user32.dll!DispatchClientMessage()
user32.dll!__fnEMPTY()

I don't believe that SolidWorks is doing anything to cause the problem, but that something with the SolidWorks icon generator is triggering a race condition between CChangedDialog::ChangedStatusThread() and the main GUI thread. I tried 2 things:

1) I replace the call to OnBnClickedRefresh() in CChangedDialog::OnInitDialog(), with ChangedStatusThread(), avoiding the separate thread. In this case, the dialog initialized properly without hanging.

2) I reverted the change above, and added a Sleep(5000) as the first line of CChangedDialog::ChangedStatusThread(). In this case, the dialog initialized correctly at first, but after 5 seconds, when the thread continued, the dialog went to its "busy" state, and hung again.

When I have a bit more time, I'm going to try removing the call to OnBnClickedRefresh() from CChangedOnInitDialog() so the dialog starts up without the list of files, and then use "Refresh" to populate it. I expect this to hang when I press "Refresh".

I'm then going to change CChangedDialog::OnBnClickedRefresh() to call ChangedStatusThread() directly without creating the separate thread. I expect this to work fine.

Let me know if there's anything else you'd like me to test.

Terry

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3048015

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-02-07 20:01:05 CET