[nautilus] Clarify the reason for recent nautilus_file_peek_display_name() workaround



commit e7b6fd0e59ec49fbe6216c157eea2a92b384d39e
Author: Tomas Bzatek <tbzatek redhat com>
Date:   Thu Jan 27 14:38:44 2011 +0100

    Clarify the reason for recent nautilus_file_peek_display_name() workaround

 libnautilus-private/nautilus-file.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
---
diff --git a/libnautilus-private/nautilus-file.c b/libnautilus-private/nautilus-file.c
index a1b738a..e531dd8 100644
--- a/libnautilus-private/nautilus-file.c
+++ b/libnautilus-private/nautilus-file.c
@@ -3669,6 +3669,10 @@ nautilus_file_peek_display_name (NautilusFile *file)
 	const char *name;
 	char *escaped_name;
 
+	/* FIXME: for some reason we can get a NautilusFile instance which is
+	 *        no longer valid or could be freed somewhere else in the same time.
+	 *        There's race condition somewhere. See bug 602500.
+	 */
 	if (file == NULL || nautilus_file_is_gone (file))
 		return "";
 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]