2009/1/31 John Darrah <xyllyx_at_gmail.com>:
> On Sat, Jan 31, 2009 at 08:36:48AM +0100, Stefan K??ng wrote:
>> John Darrah wrote:
>> > On Fri, Jan 30, 2009 at 11:39:31AM +0100, Stefan K??ng wrote:
>> >> John Darrah wrote:
>> >>> Version 1.5.7
>> >>>
>> >>> How to reproduce:
>> >>>
>> >>> Select "Checkout".
>> >>> Pick the upper "[...]" button.
>> >>> Type in bogus server that cannot be contacted (into the browser URL).
>> >>> Wait for error message.
>> >>> Then pick the "OK" button. (the browser window closes)
>> >>> Then note that the upper "[...]" button in Checkout dialog is a white blob.
>> >>> Try something like just moving the Checkout dialog
>> >>> Note that it is not responding.
>> >>> Wait for 20 minutes... still not responding.
>> >>> Kill Checkout dialog.
>> >>>
>> >>> This was in 1.5.6 too. (reported on 12/24/08)
>> >>>
>> >>> I would expect that the OK button would not be available in the browser
>> >>> if the server connect fails.
>> >> Not reproducible, sorry.
>> >>
>> >> Also, checking the code:
>> >> * there's nothing different between you clicking "OK" or "Cancel" in the
>> >> repo browser that could cause this
>> >> * when clicking OK, the only thing different than clicking "Cancel" is
>> >> that the url shown in the repo browser is inserted into the edit box of
>> >> the checkout dialog - that's ALL.
>> >>
>> > In addition to my last post, I just noticed that when it is
>> > in the hung state that TortoiseProc.exe is consuming 97% CPU
>> > in the task manager.
>>
>> Are you sure that no virus scanner is messing around? It might get
>> confused due to the unreachable url?
>> What url did you use? Maybe it has to be a special url to trigger this?
>>
>> Stefan
>>
> One machine is XP Home (my home machine), No antivirus,
> running as Limited User. One machine is XP Pro with Symantec
> AV. domain login, Power user (my work). One machine is XP
> Embedded, no AV, running as Administrator (also at work).
>
> I can reproduce the hang condition on all machines every
> time I try.
>
> The first time I noticed this I had accidentally mis-typed
> the -real- server name. Since then I have been using
> "svn://bogus.server" as a test case.
I just tried this with a nightly build (admittedly an old one) and I
don't see this either. Can you please check that the reproduction
recipe you have given is exactly right. What is the error you see in
repo browser? Is the repo browser still responsive? After you click OK
in the repo browser, you do nothing else at all?
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1082335
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-01 00:24:56 CET