unity-scope-loader is adding the SAME inotify watches regularly every 4 seconds

Bug #1301984 reported by Colin Ian King
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libunity
New
High
Unassigned
libunity (Ubuntu)
New
High
Unassigned

Bug Description

unity-scope-loader is adding the SAME inotify watches regularly every 4 seconds:

Inotify watches added:
  PID Process Rate/Sec File
  3495 unity-scope-loader 0.250 /usr/share/upstart/xdg/menus/unity-lens-applications-merged
  3495 unity-scope-loader 0.250 /etc/xdg/menus/unity-lens-applications-merged
  3495 unity-scope-loader 0.250 /usr/share/upstart/xdg/menus
  3495 unity-scope-loader 0.250 /usr/local/share/applications
  3495 unity-scope-loader 0.250 /usr/share/ubuntu/applications
  3495 unity-scope-loader 0.250 /home/king/.config/menus/unity-lens-applications-merged
  3495 unity-scope-loader 0.250 /etc/xdg/xdg-ubuntu/menus
  3495 unity-scope-loader 0.250 /etc/xdg/xdg-ubuntu/menus/unity-lens-applications-merged

I'm seeing every 4 seconds the *same* files being added to an inotify watch. Additionally, the code is polling every 4 seconds to do this:

Top polling system calls:
  PID Process Syscall Rate/Sec Infinite Zero Minimum Maximum Average
                                                           Timeouts Timeouts Timeout Timeout Timeout
  3476 unity-scope-loader poll 0.0167 2 3 0.0 sec 0.0 sec 0.0 sec
  3495 unity-scope-loader poll 0.2500 0 0 4.0 sec 4.0 sec 4.0 sec
 Total 0.2667 2 3

the timeout is set to just 4 seconds. Is this heavy polling and repeated inotify watch adding really required? We're trying to get the battery life to last longer and this kind of polling activity just is rather anti-social if it is not necessary.

Attached are the results of a 5 minute analysis from the health-check too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 3 15:14:14 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-03-25 (9 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
SourcePackage: libunity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in libunity (Ubuntu):
importance: Undecided → High
Changed in libunity:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.