This bug is related to 4160.

After launching the current Nautilus build (6pm, Sat, Oct 28th), and using it to
connect to services, both browsing URLs w/ Mozilla and browsing local URIs start
to fail.  Clicking on any button that represents a URI puts Nautilus is a hung
state with the throbber going.  No output is available in the terminal.

I have a feeling this is going to be a hard bug to reproduce once I shut down
this copy of Nautilus and start up a new copy, but I'm reporting the bug anyway.



------- Additional Comments From bfrank@eazel.com 2000-10-29 17:17:06 ----

Ok...so I have been able to reproduce this every time on my machine.  It takes
about 2 minutes of browsing services, and then everything goes nuts.




------- Additional Comments From sullivan@eazel.com 2000-10-30 07:53:31 ----

cc:ing this obviously critical bug to a couple more people. We'll see whether
others can reproduce it. A specific set of steps to reproduce would be
invaluable here.



------- Additional Comments From sullivan@eazel.com 2000-10-30 10:52:38 ----

Probably the same underlying bug as 4160. Darin and I are working on this.



------- Additional Comments From sullivan@eazel.com 2000-10-30 11:48:42 ----

Darin and I figured out the problem, now Darin is going to figure out a good
fix. The problem is that some gnome_vfs_async calls (specifically
gnome_vfs_async_load_directory in this case) don't get a handle set because they
fail really early (e.g., making a gnome_vfs_uri out of "eazel:"). Then the code
in nautilus_directory_async that relies on the existence of the handle to know
that the job is in progress doesn't see a handle, and starts a second identical
job. This causes the async_job_count to get out of whack, which eventually gets
to a state where no new async jobs are started.



------- Additional Comments From sullivan@eazel.com 2000-10-30 14:12:59 ----

Here are steps to reproduce:
(1) Launch Nautilus
(2) Click "Services" button, wait for contents to appear.
(3) Click "Home" button, wait for contents to appear.
(4) repeat steps (2) and (3) three additional times, so you've clicked each
button four times in total. On my machine, the fourth click on "Home" will be
the one that fails (contents never appear, throbber never stops), and from that
time forward, navigation will fail.



------- Additional Comments From bfrank@eazel.com 2000-11-06 11:26:25 ----

No longer seeing the problematic behavior.  Marking verified.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:44 -------
Bug blocks bug(s) 44160.

The original reporter (bfrank@eazel.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.