Opened 14 years ago

Last modified 13 years ago

#955 closed Bug report

Race condition on local directory open

Reported by: paul_galbraith Owned by: Alexander Schuch
Priority: normal Component: FileZilla Client
Keywords: Cc: paul_galbraith, Alexander Schuch, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

I have a local virtual drive (not a windows share, but a
clearcase version control view) mapped on my windows
machine. FZ 2.2.16 gets into a race condition when I
navigate three levels down into this drive, after opening a
folder that has ~100 subfolders.

Change History (8)

comment:1 Changed 14 years ago by Tim Kosse

What exactly is the problem? Please be more specific. Please
reopen item after giving more information.

comment:2 Changed 14 years ago by paul_galbraith

Hi, do you know what I mean by race condition? CPU goes
to 100% usage and never recovers. FileZilla needs to be
manually killed; that is the problem.

comment:3 Changed 14 years ago by paul_galbraith

Hi, do you know what I mean by race condition? CPU goes
to 100% usage and never recovers. FileZilla needs to be
manually killed; that is the problem.

comment:4 Changed 14 years ago by Tim Kosse

That's not a race condition, that seems to be an infinite loop.
http://en.wikipedia.org/wiki/Race_condition
http://en.wikipedia.org/wiki/Endless_loop

comment:5 Changed 14 years ago by paul_galbraith

Cheers, but a race condition can ultimately exhibit the same
symptoms, a thread looking for a condition that's not going
to occur because of outside thread/process influence....I'm
betting that you guys haven't coded an infinite loop ... at
any rate, this could be argued a lot of ways, and the end
result is the same :-)

comment:6 Changed 13 years ago by Alexander Schuch

Can you please try most recent FileZilla 2 or even better FileZilla 3 (beta) to check if the problem still occurs?

comment:7 Changed 13 years ago by paul_galbraith

I've long since forgotten the exact conditions under which I had this problem. Seeing as nobody seems to have had the same problem, I'll close this issue.

comment:8 Changed 13 years ago by paul_galbraith

I've long since forgotten the exact conditions under which I had this problem. Seeing as nobody seems to have had the same problem, I'll close this issue.

Note: See TracTickets for help on using tickets.