GNOME Bugzilla – Bug 357721
High cpu usage in nautilus
Last modified: 2006-10-29 17:29:50 UTC
Please describe the problem: When copying a file into a folder, having that folder open in nautilus and refreshing 2 - 3 times causes cpu usage to skyrocket and stay there even when browsing out of folder. Killing nautilus and having it reload brings it back to normal. I found this bug also posted in the ubuntu forums. Steps to reproduce: 1. download or copy large file into another folder. 2. browse to folder file is copying into 3. hit refresh 2 - 3 times Actual results: cpu usage usually jumps to 70-95% and stays there until nautilus is killed and reloaded. Expected results: Does this happen every time? Yes, happens every time. Other information: Same bug has been reported here... https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/54684 I am using gnome 2.16 on slackware 11.0rc5
Related Ubuntu bugs: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/54684 https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/59967 https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/62100 Version: 2.16.0
I'm seeing this too... and I usually also need to kill the panel when this happens because it uses a an unnaturally big amount of memory, too...
I'm seeing this too. From attaching gdb to the process it seems nautilus gets stuck somewhere in g_main_context_iterate(). Doing an strace I get flooded with the following: time(NULL) = 1161377364 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1161377364, 832785}, NULL) = 0 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8, events=POLLIN|POLLPRI}, {fd=10, events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN}, {fd=18, events=POLLIN|POLLPRI}, {fd=17, events=POLLIN}], 13, 0) = 0
I get this too.
I'm getting this too. strace shows nautilus is POLLing a million times a second. (gdb) thread apply all bt
+ Trace 78064
Thread 2 (Thread 1132489040 (LWP 17889))
Thread 1 (Thread 47329565327152 (LWP 14587))
probably a duplicate of bug #357704, marking as duplicate. Feel free to reopen if you think that's not correct *** This bug has been marked as a duplicate of 357704 ***