Background CPU usage increases over time #5127
Comments
|
So you're saying that's a bug that should be reproducible on all platforms with all accounts? How do you measure the system load, I often leave it open for a full day but I haven't noticed this yet. If you create a new AWS instance with a new account there can't be any sensitive information in the debug log by definition. |
(I did mean *nix load average literally, as well as In this case, system load was seen as steadily increasing while being watched with: Which I then confirmed was attributed to The first few times this happened,
It appears to be reproducible in combinations of Android 10/11 and Linux 4.19/5.10, yes. I have not tested Windows or Mac OS X, let alone an iPhone (I don't have one atm to test with.)
Good point! I'll repeat this test on AWS with a new account and attach that debug log (could take up to 48 hours to reproduce. This is not a consistent increase of CPU, it appears to be a "jagged increase" if graphed.) This makes me wonder if there are background tasks or CRON-alike (scheduled / time-based) cleanup or database management, etc that is simply getting backed up, or not cleanly exiting. It's also worth noting that if
I'll also note that [damon@doom ~]$ ps aufx | grep Z
damon 10344 0.0 0.0 0 0 ? Z Mar13 4:43 | \_ [signal-desktop] <defunct>
damon 2054114 0.0 0.0 0 0 ? Z Mar21 3:38 | \_ [signal-desktop] <defunct> |
|
Honestly your config seems a bit too exotic for me not to suspect it being the root cause. Is there any chance you can reproduce that issue with a docker container? Or anything else that's easily reproducible? That'd be easier to share, I don't really want to set up signal-desktop on a AWS instance for a bug only you seem to be having. |
|
I showed the bug as happening on my desktop in case 1, and a simple
VirtualBox VM in case 2...
…On Sat., Mar. 27, 2021, 11:08 a.m. Quentin Hibon, ***@***.***> wrote:
Honestly your config seems a bit too exotic for me not to suspect it being
the root cause. Is there any chance you can reproduce that issue with a
docker container? Or anything else that's easily reproducible? That'd be
easier to share, I don't really want to set up signal-desktop on a AWS
instance for a bug only you seem to be having.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOSNPOZ2NPGIWZ5ZJDYUETTFYNJ3ANCNFSM4Z4OS74Q>
.
|
|
Is this issue still persisting under new Signal 5.0.0? Otherwise this bug could be closed. |
|
Hard to know, version 5 has not reached Fedora 33 yet (snap still shows the
version I opened this issue with.)
Will try a git version manually later and let you know.
…On Sun., Apr. 18, 2021, 4:35 a.m. Jomi Wagner, ***@***.***> wrote:
Is this issue still persisting under new Signal 5.0.0? Otherwise this bug
could be closed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOSNPNPOALHBZPPTST7CLLTJK7WPANCNFSM4Z4OS74Q>
.
|
Still occurs in 5.3.0 now that this version has arrived in the now stable Fedora 34. |
|
On OSX 11.4 I also see |
|
Pop OS 21.04, with official deb package v5.9.0, I see on my i7-5600U constant 10-13% CPU usage in top
|
|
I also observe strange behavior. I use Signal quite infrequently, so it is idle 99% of the time. Yet, when the system is idle, Signal is usually at the top of the top ;) This application performs surprising amount of activity when doing nothing and now even being displayed - it is on the desktop that is not visible at this moment. The messaging (!) application runs 8 processes, one of them has something with GPU (for God's sake, why?). I am not familiar with the internals of the app but it seems there is Chromium there. |
|
Yeah, I got tired of signal doing something questionable with my system
resources, I only run it in a very small sandbox now so that it's not
crypto mining on my computer, or whatever the hell it decides to do with my
28 cores all day long at 100%......
…On Wed., Dec. 8, 2021, 5:22 p.m. Nikolai Grigoriev, < ***@***.***> wrote:
I also observe strange behavior. I use Signal quite infrequently, so it is
idle 99% of the time. Yet, when the system is idle, Signal is usually at
the top of the top ;) This application performs surprising amount of
activity when doing nothing and now even being displayed - it is on the
desktop that is not visible at this moment. The messaging (!) application
runs 8 processes, one of them has something with GPU (for God's sake,
why?). I am not familiar with the internals of the app but it seems there
is Chromium there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOSNPLG2CS2NN2ROHDXDFDUQAAF3ANCNFSM4Z4OS74Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Same issue here with Macs Monterey 12.0.1 and Signal 5.25.1. At some point, I'll notice that my fans are getting pretty loud while doing nothing: opening the activity Monitor will every-time reveal Signal using 99% of CPU. I have to quiet the app then restart it. I'm also using what's app and Telegram in the background and Signal is the only one with such behavior. |
|
Sorry folks are running into this. We've been trying hard to get to the bottom of these issues. If you have reliable reproduction steps, deeper investigation, or even theories, we'd love to hear them! |
Reproduced on Arch, both in Beta and Release versions. I hope that it will be resolved soon, because it's critical. Maybe Ctrl+Shift+F12 chromium debugging would help? I can't open it in Signal for some reason |
|
Check out possible solution on this comment: #4459 (comment) TL;DR: disable notifications in Signal's settings |
Commented on #4459: Has anyone tried tracing gif and other media that may cause load issues if ran in the background for long period of time in several message streams? Also just a hunch if this could be related to disk usage and files as attachments to signal? |
|
After switching off notifications signal-desktop on windows (10) seems to stop eating precious CPU cycles, but when I minimize it to the system tray the "polling" starts again. I'm seeing roughly 10% on average. This should be very easy to reproduce. No such issue on Linux by the way. This is a Performance Monitor Graph from signal-desktop (5.47.0) being minimized to the system tray. The same graph is pretty much a flat line when the application window is open and showing my Note to Self conversation. Don't know, if it is relevant, but my Windows 10 is a VM with GPU passsthrough running on Linux with QEMU/KVM. More often than not my idle Windows Desktop is the top CPU hog according to conky on my Linux host (that's how I noticed). Signal-desktop is one of the reasons why. The other two are discord (also electron based) and chrome which also behaves rather badly when idle. |
|
Funny, for me this is a thing that happens on Linux, but didn't happen on
Windows 10.
But yes, if you use signal more than once every few days, say you actually
treat this as your primary messaging app, so you have tens of thousands of
messages in your database, this is 100% reproducible.
The best part? Even if I uninstall the client, and then reinstall it, which
means I have none of the messages and a clean database, the polling still
happens if I just let the program run.
It's gotten to the point where I've made a script that kills signal if it's
been idle for an hour, and automatically restarts it. I'm treating it just
like a Java server at this point.
…On Thu., Jun. 23, 2022, 11:12 p.m. Necropola, ***@***.***> wrote:
After switching off notifications signal-desktop on *windows (10)* seems
to stop eating precious CPU cycles, but when I minimize it to the system
tray the "polling" starts again. I'm seeing roughly 10-20% on average.
This should be very easy to reproduce. No such issue on Linux by the way.
—
Reply to this email directly, view it on GitHub
<#5127 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOSNPM7JHPMF3FDSEJVPDDVQVGURANCNFSM4Z4OS74Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@AlbinoGeek sorry you keep running into it. On Linux do you think you could try running with |
Bug Description
After resuming the system from standby, or simply leave the
signal-desktopapplication running for many hours, the application continues to churn through computer resources, steadily using more and more CPU over time.Steps to Reproduce
signal-desktopActual Result:
Come back to a system load above
5and entire pinned cores bysignal-desktop...This happens regardless of the number of contacts, conversations or messages in the account.
This happens regardless of using physical or virtual hardware.
This even happens in an AWS EC2 instance.
I even tried virtual linked devices to remove my phone(s) as variable(s).
Expected Result:
NEARLY ZERO background CPU usage, especially in an empty account, with no messages being received or expiring.
Screenshots
[ I will post more screenshots after leaving it to bloat itself for another 6 hours... ]
Platform Info
Combination 1 (on Physical Hardware)
Signal Version:
v1.40.1Operating System:
Fedora Workstation 33Kernel:
5.10.19-200.fc33.x86_64Linked Device Version:
Android 11Kernel:
4.19.113-20937596Combination 2 (KVM Virtual Machine)
Signal Version:
v1.40.1Operating System:
Fedora Workstation 33Kernel:
5.10.19-200.fc33.x86_64Linked Device Version:
Android 11Kernel:
4.19.113-20937596Combination 3 (AWS EC2 t2.micro)
Signal Version:
v1.40.1Operating System:
Debian 10.8Kernel:
4.19.0-14.ec2.x86_64Linked Device Version:
Android 11Kernel:
4.19.113-20937596Combination 4 (AWS EC2 t2.micro) + Virtual Android
Signal Version:
v1.40.1Operating System:
Debian 10.8Kernel:
4.19.0-14.ec2.x86_64Linked Device Version:
Android 10Kernel:
4.19.71Link to Debug Log
Since there wasn't any information on whether a
Debug Logcontains any sensitive information... No.It's reproducible with new accounts, and on both physical and virtual machines (including on a t2.micro instance on AWS with a basic X desktop installed), so has absolutely nothing to do with my account or computer hardware.
The text was updated successfully, but these errors were encountered: