After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 357721 - High cpu usage in nautilus
High cpu usage in nautilus
Status: RESOLVED DUPLICATE of bug 357704
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-26 01:31 UTC by Donnavon Hallgren
Modified: 2006-10-29 17:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Donnavon Hallgren 2006-09-26 01:31:03 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
Comment 2 Michael Monreal 2006-10-15 17:01:04 UTC
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...
Comment 3 Dennis Jacobfeuerborn 2006-10-20 21:03:25 UTC
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
Comment 4 Nathan Hewitt 2006-10-24 05:36:17 UTC
I get this too.
Comment 5 Mark D. 2006-10-24 16:59:51 UTC
I'm getting this too. strace shows nautilus is POLLing a million times a second.

(gdb) thread apply all bt

Thread 2 (Thread 1132489040 (LWP 17889))

  • #0 __read_nocancel
    from /lib/libpthread.so.0
  • #1 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #2 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 1 (Thread 47329565327152 (LWP 14587))

  • #0 g_main_context_find_source_by_id
    from /usr/lib/libglib-2.0.so.0
  • #1 g_source_remove
    from /usr/lib/libglib-2.0.so.0
  • #2 gnome_vfs_get_special_mime_type
    from /usr/lib/libgnomevfs-2.so.0
  • #3 gnome_vfs_monitor_callback
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 POA_Nautilus_MetafileMonitor__init
  • #9 __libc_start_main
    from /lib/libc.so.6
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 g_main_context_find_source_by_id
    from /usr/lib/libglib-2.0.so.0

Comment 6 Sebastien Bacher 2006-10-29 17:29:50 UTC
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 ***