I've not had a chance to read every comment in this bug in detail yet, but it seems that the backtraces provided were from running Nautilus with sudo. There should be no need to do this, and that might be why the backtrace doesn't show anything useful (if it is your users instance of Nautilus which has broken, then running a second instance of nautilus under GDB as a different user won't be much use)
Nautilus will exit if you run a new instance when there is already one running in your session, so you can't just run "gdb nautilus". You need to attach GDB to the instance of nautilus which is already running in your session. The procedure for doing this is documented in https://wiki.ubuntu.com/Backtrace#Already%20running%20programs Please try and do this (only when Nautilus is consuming a lot of CPU). It also helps sometimes to interrupt and obtain a backtrace several times, to make sure that it is interrupted in roughly the same code path each time. ** Changed in: nautilus (Ubuntu) Status: Triaged => Incomplete -- Nautilus uses 100% cpu after downloading torrent https://bugs.launchpad.net/bugs/492810 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
