Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heavy Resource Demands on Login #765

Closed
NWRichmond opened this issue Nov 25, 2019 · 1 comment
Closed

Heavy Resource Demands on Login #765

NWRichmond opened this issue Nov 25, 2019 · 1 comment

Comments

@NWRichmond
Copy link

NWRichmond commented Nov 25, 2019

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="19.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.10"
VERSION_ID="19.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
tracker-miner-fs:
Installed: 2.3.0-1
Candidate: 2.3.0-1
Version table:
*** 2.3.0-1 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
On startup, something is eating up CPU for 5-10 minutes before simmering down, causing my CPU fan to run hard. It looks like the process in question might be tracker-miner-fs.

Behavior on Startup
pop-os-cpu-100-01

pop-os-cpu-100-processes-01

After 5-10 Minutes

pop-os-cpu-normal-01

pop-os-cpu-normal-processes-01

Steps to reproduce (if you know):

Normal startup & login.

Expected behavior:

Absence of large CPU load on login (& 5-10 minutes after).

Other Notes:

Running on a 2019 System76 Darter Pro w/ Intel Core i7-8565U CPU & 32 GB RAM

All packages are up-to-date.

Appears to have been happening for at least the last few days (maybe a week), with packages updated through Pop!_Shop daily.

@NWRichmond
Copy link
Author

Not happening anymore, and I have no clue which update might have addressed this. The problem went as quickly as it came.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant