StewPedassle It seems to me that while you are in the debugger you hit Ctrl+C after nautilus has finished hogging your system. This is not good because it gives the backtrace of a "sleeping" process, which is not interesting. You should interrupt nautilus while it is actively using the CPU.
I suggest running the debugger several times; each time you hit Ctrl+C nautilus will be stopped at a different time and different backtraces will be obtained. You can even do this in a single gdb run. Instead of quiting gdb, continue and repeat the interrupting and backtrace. (gdb) continue <Ctrl+C again> (gdb) backtrace full ... etc. -- Nautilus Loads Processor https://bugs.launchpad.net/bugs/316924 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
