systemd-journald process CPU 100%
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xdg-desktop-portal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello.
The 'systemd-journald' process occupies the CPU.
CPU usage rate 100%.
Hard disk that was used about 4GB increased to 9GB or more after reboot.
Q: How do I restore the hard disk capacity?
When this symptom occurred, I thought it was attacked by Ransome-ware.
This is a Serious problem.
Can not work properly when CPU usage is high.
Opening the terminal takes a while too.
The the system froze. Mouse does not move, so press the reboot switch to reboot.
You say it's a good Ubuntu because it's stable.
Since Ubuntu is stable, why not?
I installed Ubuntu 17.10 64bit and installed driver updates (proprietary Intel microcode and NVIDIA drivers) and Ubuntu updates.
I did not install the software separately, nor did i tweak the program.
I just installed Ubuntu and watched it one by one.
There is certainly a bug in the process of moving the 'systemd-journald' itself or the 'systemd-journald'.
Please fix it.
best regards.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xdg-desktop-portal 0.8-2
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 20:48:15 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=ko_KR.UTF-8
PATH=(custom, no user)
SHELL=/bin/sh
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x55de984b0508: mov 0x8(%rax),%rcx
PC (0x55de984b0508) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: xdg-desktop-portal crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1691649, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.