Bug 1329662

Summary: nautilus service periodically turns into CPU hog
Product: [Fedora] Fedora Reporter: Alan Jenkins <alan.christopher.jenkins>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: cosimo.cecchi, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9f99083372ad699acbe34cdda56cecfa26651e34
Whiteboard: abrt_hash:92b8ed55f8f312613faaa8c0316a28ca291819ff;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 20:06:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alan Jenkins 2016-04-22 14:06:58 UTC
Version-Release number of selected component:
nautilus-3.18.5-1.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: poll
executable:     /usr/bin/nautilus
global_pid:     4287
kernel:         4.5.1-300.vanilla.knurd.1.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 4 (5 frames)
 #0 poll at ../sysdeps/unix/syscall-template.S:84
 #1 g_main_context_poll at gmain.c:4135
 #3 g_main_context_iteration at gmain.c:3901
 #4 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:82
 #5 g_thread_proxy at gthread.c:778

Comment 1 Alan Jenkins 2016-04-22 14:07:03 UTC
Created attachment 1149753 [details]
File: backtrace

Comment 2 Alan Jenkins 2016-04-22 14:07:04 UTC
Created attachment 1149754 [details]
File: cgroup

Comment 3 Alan Jenkins 2016-04-22 14:07:05 UTC
Created attachment 1149755 [details]
File: core_backtrace

Comment 4 Alan Jenkins 2016-04-22 14:07:07 UTC
Created attachment 1149756 [details]
File: dso_list

Comment 5 Alan Jenkins 2016-04-22 14:07:08 UTC
Created attachment 1149757 [details]
File: environ

Comment 6 Alan Jenkins 2016-04-22 14:07:09 UTC
Created attachment 1149758 [details]
File: limits

Comment 7 Alan Jenkins 2016-04-22 14:07:12 UTC
Created attachment 1149759 [details]
File: maps

Comment 8 Alan Jenkins 2016-04-22 14:07:14 UTC
Created attachment 1149760 [details]
File: mountinfo

Comment 9 Alan Jenkins 2016-04-22 14:07:15 UTC
Created attachment 1149761 [details]
File: namespaces

Comment 10 Alan Jenkins 2016-04-22 14:07:16 UTC
Created attachment 1149762 [details]
File: open_fds

Comment 11 Alan Jenkins 2016-04-22 14:07:18 UTC
Created attachment 1149763 [details]
File: proc_pid_status

Comment 12 Alan Jenkins 2016-04-22 14:07:19 UTC
Created attachment 1149764 [details]
File: var_log_messages

Comment 13 Alan Jenkins 2016-04-22 14:36:42 UTC
ABRT what did you do.

Periodically the nautlius service turns into a CPU hog, e.g. it burns through half an hour of CPU time (and I notice because the laptop gets hot & noisy).  This is without any nautilus windows being open.  Feels like it's gone on for at least a month.

%Cpu(s): 21.8 us,  1.0 sy,  0.0 ni, 77.1 id,  0.1 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  3840320 total,  1516012 free,   965876 used,  1358432 buff/cache
KiB Swap:  2441400 total,  2441400 free,        0 used.  2533476 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND     
 4287 alan      20   0 1178464  34012  26776 S  93.8  0.9  33:53.13 nautilus 

So I tricked ABRT into backtracing it for me...

Hmm, I remember it looking like this.  tracker-y.  I wanted to remember to check `strace`, in case that showed anything.  Also it's SQL-y and maybe running an FTS query.

open_fds is interesting.  The tracker DB is open but no other files, which suggests it's _not_ a problem during an indexing run as such.

I've installed and enabled atop + psacct, so I should at least be able to see what time it started spinning (wall-clock time).

Comment 14 Fedora End Of Life 2016-11-25 07:26:43 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2016-12-20 20:06:08 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.