Comment 10 for bug 187547

I can confirm this bug, Its rather crippling...it can be reproduced by opening a nautilus window and changing directory by double clicking a folder.
The hang also occurs sporadically when there is an open nautilus window. When the hang occurs, it takes ~14 seconds to eat through my 4 Gb of ram, after which my computer becomes increasingly unresponsive.
I attached gdb to nautilus by the command:
gdb nautilus 7779
The only interesting message was:
0x00000000ffffe410 in ?? () from /lib64/ld-linux-x86-64.so.2
which occured before I induced the hang in nautilus
then obtained a backtrace after inducing the error.
sadly, the backtrace is identical to a backtrace performed when nautilus is not failing:
(gdb) bt
#0 0x00000000ffffe410 in ?? () from /lib64/ld-linux-x86-64.so.2
#1 0x00000001ffb782f8 in ?? ()
#2 0xf78bbc6700000004 in ?? ()
#3 0xf7ad7a1b00000000 in ?? ()
#4 0x00000001f7b4f248 in ?? ()
#5 0xffb7835800000004 in ?? ()
#6 0x080b7908f7adc176 in ?? ()
#7 0x0000000100000004 in ?? () from /lib64/ld-linux-x86-64.so.2
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I'm running x86_64 on a fresh install (as of today)
If you need any more info, or did the debugging wrong, lemme know (I'm new at this)