Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
pageserver,safekeeper: disable heap profiling (#10268)
## Problem Since enabling continuous profiling in staging, we've seen frequent seg faults. This is suspected to be because jemalloc and pprof-rs take a stack trace at the same time, and the handlers aren't signal safe. jemalloc does this probabilistically on every allocation, regardless of whether someone is taking a heap profile, which means that any CPU profile has a chance to cause a seg fault. Touches #10225. ## Summary of changes For now, just disable heap profiles -- CPU profiles are more important, and we need to be able to take them without risking a crash.
- Loading branch information
b33299d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7366 tests run: 7002 passed, 1 failed, 363 skipped (full report)
Failures on Postgres 16
test_storage_controller_many_tenants[github-actions-selfhosted]
: release-x86-64Flaky tests (4)
Postgres 16
test_physical_replication_config_mismatch_too_many_known_xids
: release-arm64test_scrubber_physical_gc_ancestors[None]
: release-arm64Postgres 15
test_physical_replication_config_mismatch_max_locks_per_transaction
: release-arm64Postgres 14
test_parent_within_horizon
: release-arm64Code coverage* (full report)
functions
:31.2% (8403 of 26942 functions)
lines
:47.9% (66690 of 139148 lines)
* collected from Rust tests only
b33299d at 2025-01-03T17:55:20.169Z :recycle: