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 470624 - Nautilus Crashes with recursive symlinks
Nautilus Crashes with recursive symlinks
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 512880 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-27 07:43 UTC by Jonathan Isom
Modified: 2008-08-17 14:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Jonathan Isom 2007-08-27 07:43:06 UTC 
I have a set of 2 symlinks in multiple locations. link a points to link b, and
link b points to link a. when i open a directory containing this nautilus
crashes instantly. 

Reproducible: Always

Steps to Reproduce:
1.ln -s /tmp/a /tmp/b
2.ln -s /tmp/b /tmp/a
3.nautilus /tmp

Actual Results:  
instant crash

Expected Results:  
Display directory
Comment 1 Cosimo Cecchi 2007-09-01 12:43:44 UTC 
I can reproduce this crash also on nautilus 2.19.91, although I don't get how useful can be to have fake recursive symlinks like that.
Comment 2 Cosimo Cecchi 2008-02-04 12:16:47 UTC 
*** Bug 512880 has been marked as a duplicate of this bug. ***
Comment 3 A. Walton 2008-05-06 00:05:57 UTC 
Can't reproduce with Nautilus 2.22. Maybe this was fixed with the GIO move? Can anyone else confirm?
Comment 4 Jonathan Isom 2008-05-06 02:25:52 UTC 
It looks good to me here.
Thanks
Comment 5 Arun Raghavan 2008-05-20 05:10:14 UTC 
Still reproducible here with Nautilus 2.22.2
Comment 6 A. Walton 2008-05-20 05:37:08 UTC 
If you can reproduce it, please provide a stacktrace of the crash.
Comment 7 Arun Raghavan 2008-05-20 07:30:07 UTC 
Sorry I wasn't clearer. Nautilus actually starts consuming 100% CPU and freezes up. I got the following traceback in gdb. If someone could tell me what libraries I need to build with debug support, I can try to get a more detailed traceback.

(gdb) thread apply all bt

+ Trace 198189

Thread 1 (Thread 0xb5fda6e0 (LWP 17826))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait_private
    from /lib/libc.so.6
  • #2 _L_lock_79
    from /lib/libc.so.6
  • #3 ptmalloc_lock_all
    from /lib/libc.so.6
  • #4 fork
    from /lib/libc.so.6
  • #5 fork
    from /lib/libpthread.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 check_match.8663
    from /lib/ld-linux.so.2
  • #10 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #11 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #13 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #14 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #15 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #16 <signal handler called>
  • #17 _int_malloc
    from /lib/libc.so.6
  • #18 _int_realloc
    from /lib/libc.so.6
  • #19 realloc
    from /lib/libc.so.6
  • #20 g_realloc
    from /usr/lib/libglib-2.0.so.0
  • #21 g_string_insert_len
    from /usr/lib/libglib-2.0.so.0
  • #22 g_string_append_len
    from /usr/lib/libglib-2.0.so.0
  • #23 ??
    from /usr/lib/libglib-2.0.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ?? 






Comment 8


Arun Raghavan





          2008-08-17 14:10:11 UTC
        



I don't see this on a freshly installed system with nautilus 2.22.5.1.