After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 41841 - Deal with a component that blocks or hangs
Deal with a component that blocks or hangs
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: Extension Library
unspecified
Other Linux
: Normal normal
: future
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2000-07-31 15:02 UTC by John Sullivan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Sullivan 2001-09-10 00:34:03 UTC 
This was split off from bug 40762, because it needs to be addressed in a different
way than crashing components. If indeed it *needs* to be addressed at all, which
isn't really clear to me.

Darin suggested maybe a timeout of some sort to deal with the infinite-loop type
of hang. I don't know if that approach makes sense for blocking-type hang.



------- Additional Comments From eli@eazel.com 2000-10-16 19:42:44 ----

Batch-assigning QA ownership of remaining bugs to eli@eazel.com



------- Additional Comments From mjs@noisehavoc.org 2000-11-15 19:17:22 ----

noit sure how much work is needed in this area




------- Additional Comments From mjs@noisehavoc.org 2000-12-04 21:12:45 ----

This bug is extremely open-ended and as such I think a candidate for deferral.
It's hard to even tell allthe ways a component _could_ hang.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:34 -------
Comment 1 John Fleck 2002-01-05 04:18:41 UTC 
Changing to "old" target milestone for all bugs laying around with no milestone set.
Comment 2 Dave Camp 2002-10-31 23:46:09 UTC 
What mjs said.