[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784450851574.jpg (198.89 KB, 1024x1024, img_1784450812329_79zfmncp.jpg)ImgOps Exif Google Yandex

894eb No.1978

the latest update seems to have a persistent memory leak whenever we run the
system_check.sh
script. does anyone know if there is a temporary patch available for this issue or if we should just revert to the previous stable version?

5fb55 No.1979

File: 1784451529009.jpg (171.53 KB, 1024x1024, img_1784451513342_9j3mtyls.jpg)ImgOps Exif Google Yandex

>>1978
reverting is a pain if you have too many config changes, but ive found that adding export telemetry_log_level=error to your environment before running the script stops the buffer from bloating. it doesnt fix the underlying leak, but it keeps the process from hitting the oom killer during long checks. are you seeing the usage climb linearly or does it jump in huge chunks? ⚡


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">