I tried to follow the steps for backtracing, but the gdb became unresponsive when nautilus crashes. Here's what happens: I use pidof to find nautilus's pid, then I start gdb and follow the steps to attach to nautilus, that works, I enter continue, and I focus on the problematic file in nautilus. Then nautilus starts hogging memory, but it's still responsive for several minutes, although slow. Finally, Nautilus hits around 75 of system memory and that's when it also hogs cpu and becomes unresponsive. I try to hit ctrl-c in gdb, but nothing happens, and gdb is unresponsive, and I'm forced to kill first nautilus (in gdb nothing happens) and then gdb.
The file I attached is what I see in gdb's terminal. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/30245808/gdb-nautilus.txt -- nautilus hangs consuming lots of memory and cpu when opening large video files https://bugs.launchpad.net/bugs/412040 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
