Summary: | dev-qt/qt-creator-3.4.0[systemd] eats 100% CPU | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cyril <cyril.baletaud> |
Component: | Current packages | Assignee: | Davide Pesavento <pesa> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | me, qt |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cyril
2015-04-28 13:16:00 UTC
Is systemd-journald running? yes it's running systemctl status systemd-journald ● systemd-journald.service - Journal Service Loaded: loaded (/usr/lib64/systemd/system/systemd-journald.service; static; vendor preset: enabled) Active: active (running) since mer. 2015-04-29 17:25:04 CEST; 10min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 110 (systemd-journal) Status: "Processing requests..." CGroup: /system.slice/systemd-journald.service └─110 /usr/lib/systemd/systemd-journald avril 29 17:25:04 gentoocyril systemd-journal[110]: Runtime journal is using 8.0M (max allowed 396.1M, trying to leave 594.1M free of 3.8G available → current limit 396.1M). avril 29 17:25:04 gentoocyril systemd-journal[110]: Runtime journal is using 8.0M (max allowed 396.1M, trying to leave 594.1M free of 3.8G available → current limit 396.1M). avril 29 17:25:04 gentoocyril systemd-journal[110]: Journal started avril 29 17:25:04 gentoocyril systemd-journal[110]: Missed 85 kernel messages avril 29 17:25:04 gentoocyril systemd-journal[110]: Permanent journal is using 584.1M (max allowed 4.0G, trying to leave 4.0G free of 65.6G available → current limit 4.0G). avril 29 17:25:04 gentoocyril systemd-journal[110]: Time spent on flushing to /var is 178.270ms for 768 entries. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable Well, this needs to go upstream as I don't think it's gentoo-specific. upstream patch available: https://bugreports.qt.io/browse/QTCREATORBUG-14356 https://codereview.qt-project.org/#/c/115484/ works for me... I know, that patch is in 3.5.0 which I will bump asap. |