ydb/contrib/libs/tcmalloc, branch CLI_2.26.0Mirror of YDB github reposhttps://code.mastervirt.ru/ydb/atom?h=CLI_2.26.02025-09-22T22:06:25ZFix broken TCMalloc options.2025-09-22T22:06:25Zakhropovakhropov@yandex-team.com2025-09-22T21:26:07Zurn:sha1:863e0ecfae70fe7bd74268de2ed93bdd3a0bed07
Update build flags that were not updated together with the update of TCMalloc.
* TCMALLOC_256K_PAGES -> TCMALLOC_INTERNAL_256K_PAGES
* TCMALLOC_NUMA_AWARE -> TCMALLOC_INTERNAL_NUMA_AWARE
* TCMALLOC_LARGE_PAGES -> TCMALLOC_INTERNAL_32K_PAGES
* TCMALLOC_SMALL_BUT_SLOW -> TCMALLOC_INTERNAL_SMALL_BUT_SLOW
commit_hash:d4f51f0940dff02ac15d1a65b8c112260facd566
YT-25994 Fix data race in user data support2025-08-28T17:58:15Zmikailbagmikailbag@yandex-team.com2025-08-28T17:21:42Zurn:sha1:e453cbf2e074f1323d976fb2f0cf0a55c39022ca
This patch fixes data race on user data in SampleRecorder::PushDead by adding necessary locking.
As a drive-by change, SetSampleUserDataCallbacks documentation now describes guarantees and requirements for the callbacks, including several not obvious ones.
commit_hash:7ffea42883c9344829edd50c795243f56f1e7f3c
YT-24366 Fix lock acquisition order2025-08-13T13:05:48Zmikailbagmikailbag@yandex-team.com2025-08-13T12:16:25Zurn:sha1:0a494f5c53ebd18bc9b89cd9b4375abf38f80482
There are several implied requirements "lock X must be acquired before lock Y". It turned out that one of these requirements (namely, first) was not respected, leading to deadlocks.
commit_hash:1bf33d46c54bfb41390a1937b4ef44939b88c672
Intermediate changes2025-08-11T16:11:48Zrobot-pigletrobot-piglet@yandex-team.com2025-08-11T15:49:39Zurn:sha1:ff86b9be2dd6abd6c11088cb34fbfb735d46feaf
commit_hash:3721d11af212a52f43d2c133b98aabd2ac47a983
Intermediate changes2025-08-07T16:36:57Zrobot-pigletrobot-piglet@yandex-team.com2025-08-07T16:24:44Zurn:sha1:319c53daa4d3137edd9f6938531c983331ae730e
commit_hash:da32df476c05ee8928d99ec0d784ed2e3b929624
Intermediate changes2025-08-07T14:09:15Zrobot-pigletrobot-piglet@yandex-team.com2025-08-07T13:52:35Zurn:sha1:a246d60d3b3ac79dc02ab9535b4c9aa188ce7e77
commit_hash:f0dc5f57e17d0f15ccbb92d7ced5a11008765dc5
Intermediate changes2025-06-26T09:23:13Zrobot-pigletrobot-piglet@yandex-team.com2025-06-26T08:41:25Zurn:sha1:9862e1947bb5258751618ee2f2a992ba5d6ae2a3
commit_hash:53a87bd83ce2def857ef518c4e6c591f98d9ac3d
Redeprecate undeprecated APIs2025-06-26T09:03:06Zmikailbagmikailbag@yandex-team.com2025-06-26T08:05:14Zurn:sha1:4c70517404cd2542509131c67dd764a3673bb228
commit_hash:0b5b73389c4399c46783591ed54dadb5f6c72f62
Respect user data when hashing samples2025-06-10T18:05:41Zmikailbagmikailbag@yandex-team.com2025-06-10T17:35:32Zurn:sha1:2851ed080b67be3b38a07bca1da9da9924bdc61b
Currently allocation sampling code does not account for user-data in samples, so two samples differing only in user data are treated the same. It can negatively affect quality of resulting profiles. This patch effectively rebases [YTSaurus patch](https://github.com/ytsaurus/ytsaurus/commit/7fbc80bd10915c8703b9651eca3bacc96e034a12) on current TCMalloc version, fixing the issue.
commit_hash:82c18820f5c890b8b851df8e3c6ee779144690a0
Fix user data lifetime bug2025-06-03T19:02:22Zmikailbagmikailbag@yandex-team.com2025-06-03T17:57:45Zurn:sha1:3de0a42adb64f435508e027547a2a90bf53ff74d
Profile previously have not extended lifetime for user data referenced by contained allocations. Such data could be destroyed too early, potentially during deallocation, rendering user_data pointer invalid (and thus making the whole feature effectively unusable).
As a fix, profiles now act as strong pointers for all sampled allocations.
commit_hash:8f77b397661ca7eab30793aece6f2e655722e99c