chaitin / chaitin/SafeLine

[Bug] safeline-pg Abnormal resource usage

Open
#1,233 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
22.6k
Forks
1.5k
Avg merge
4h 30m
Merged PRs (30d)
11

Description

What happened?

Run safeline in debian13 (vmware) use podman-compose (lick docker)

wget "https://waf.chaitin.com/release/latest/compose.yaml"
but images is from dockehub

chaitin/safeline-postgres:15.2    #this
chaitin/safeline-detector-g:9.2.7  
chaitin/safeline-tengine-g:9.2.7   
chaitin/safeline-fvm-g:9.2.7       
chaitin/safeline-chaos-g:9.2.7     
chaitin/safeline-mgt-g:9.2.7       
chaitin/safeline-luigi-g:9.2.7   

podman stats, safeline-pg takes up too much CPU and is intermittent
Image

but when i use sudo podman it looks normal , i meen safeline-pg image
i dont know why maybe bug

system info:
uname -a

Linux debi 6.12.43+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.43-1 (2025-08-27) x86_64 GNU/Linux

podman version

Client: Podman Engine
Version: 5.4.2
API Version: 5.4.2
Go Version: go1.24.4
Built: Fri Jul 25 17:23:06 2025
Build Origin: Debian
OS/Arch: linux/amd64

lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 45 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Vendor ID: GenuineIntel
Model name: 13th Gen Intel(R) Core(TM) i9-13980HX
CPU family: 6
Model: 183
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1

free -h
    total        used        free      shared  buff/cache   available

Mem: 2.9Gi 2.3Gi 178Mi 38Mi 667Mi 623Mi
Swap: 0B 0B 0B

How we reproduce?
  1. ...
  2. ...
  3. ...
Expected behavior

No response

Error log

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the linked compose.yaml setup, comparing unprivileged and sudo podman runs and recording podman stats for safeline-pg. Check the container and PostgreSQL logs alongside the supplied Debian, Podman, CPU, and memory details. Done means the cause of the intermittent CPU usage is identified and a verified fix or clear configuration guidance is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.