-
Notifications
You must be signed in to change notification settings - Fork 16
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
segfaults every 5 seconds #28
Comments
Same here:
|
So both of you are getting segfaults in the |
|
@sghael Are you also getting segfaults in your dmesg log? Does In the two dmesg logs above, it clearly shows that If Can everyone who experiences this please post your OS version ( |
|
this seems like a potential problem Line 518 in 5dd0666
on my Ubuntu 24.04:
|
interesting:
|
Oh wow, that's very helpful, thanks! It looks like Ubuntu and Debian are shipping with a Also unusual because mine (Arch) reports the same version, but shows different default fields and doesn't segfault:
The root problem is either with procps-ng or Debian or Ubuntu, depending on whether it is patched by the distros or not, but it would be nice to find a workaround on the Circadian side in the meantime. If I get time (big if), I'll do some testing in an Ubuntu VM and see if I can reproduce and work around it. |
Ok, it's upstream and it was already patched 11 months ago, but not released yet. It has something to do with the systemd environment, which is probably why only some of us hit it. Patch in procps-ng: https://gitlab.com/procps-ng/procps/-/commit/79042e07fab9956135a21b1df7a69d1fbde7ef79 |
yep, that's it. Thanks for finding the upstream bug. I'm looking at the circadian code and wonder if it solves the problem if
|
Yes, dropping But now that I see what it's doing, I'm going to look into bypassing |
I am running Debian sid (Linux 6.7.9-amd64) and getting these errors every 5 seconds.
The text was updated successfully, but these errors were encountered: