Page 260 - 《软件学报》2026年第3期
P. 260

李清伟 等: Go  语言程序的内存性能与安全问题实证研究                                                   1223


                 [44]   grpc. Ticker leak in weighted round robin picker creation. 2025. https://github.com/grpc/grpc-go/issues/6642
                 [45]   grpc. Ticker leak in weighted round robin picker creation. 2025. https://github.com/grpc/grpc-go/issues/6642#issuecomment-1723821389
                 [46]   PingCAP. DATA RACE in the TestHistoryReadInTxn. 2025. https://github.com/pingcap/tidb/issues/34666
                 [47]   btcsuite. rpcclient: Make sure batch requests are GCed. 2025. https://github.com/btcsuite/btcd/pull/2105
                 [48]   grpc. Established streams leak. 2025. https://github.com/grpc/grpc-go/issues/2444
                 [49]   Kubernetes SIGs. ClusterCacheTracker: Memory leak when kubeconfig is rotated too often, and CAPI is running on the workload cluster.
                     2025. https://github.com/kubernetes-sigs/cluster-api/issues/9542
                 [50]   Go. The Go programming language specification—Slice expressions. 2025. https://go.dev/ref/spec#Slice_expressions
                 [51]   PingCAP. Memory leak after executing large transaction. 2025. https://github.com/pingcap/tidb/issues/13883
                 [52]   PingCAP. Unstable test in the TestConstraintCheckForUniqueIndex. 2025. https://github.com/pingcap/tidb/issues/32412
                 [53]   Pomerium. core/hpke: Reduce memory usage from zstd. 2025. https://github.com/pomerium/pomerium/pull/4650/files
                 [54]   PingCAP. Use iterator in show ddl jobs to avoid oom when there is too many history ddl jobs. 2025. 2025. https://github.com/pingcap/tidb/
                     pull/12472
                 [55]   PingCAP. TiDB. 2025. https://github.com/pingcap/tidb
                 [56]   CockroachDB.  roachtest:  sqlsmith/setup=empty/setting=no-mutations  failed.  2025.  https://github.com/cockroachdb/cockroach/issues/
                     48092
                 [57]   Milvus. Datacoord crash with panic: runtime error: invalid memory address or nil pointer dereference. 2025. https://github.com/milvus-io/
                     milvus/issues/17823
                 [58]   Milvus. Server crashed during inserting. 2025. https://github.com/milvus-io/milvus/issues/5333
                 [59]   Milvus. Querycoord crash during test after reinstallation. 2025. https://github.com/milvus-io/milvus/issues/31495
                 [60]   Uber. nilaway. 2025. https://github.com/uber-go/nilaway
                 [61]   Go. nilness. 2025. https://pkg.go.dev/golang.org/x/tools/go/analysis/passes/nilness
                 [62]   Optimism. Avail plasma. 2025. https://github.com/ethereum-optimism/optimism/pull/9811
                 [63]   Bugaev L. Fix possible memory confusion in unsafe slice cast. 2025. https://github.com/buger/jsonparser/pull/204
                 [64]   The Kubernetes Authors. Garbage Collection. 2025. https://kubernetes.io/docs/concepts/architecture/garbage-collection/
                 [65]   Milvus. Indexcoord can not be recovered after datacoord pod kill chaos test in master branch. 2025. https://github.com/milvus-io/milvus/
                     issues/19263
                 [66]   Milvus.  Datacoord  keep  crash  when  doing  bulk  load  after  datacoord  pod  kill  chaos  test.  2025.  https://github.com/milvus-io/milvus/
                     issues/19715
                 [67]   Wikipedia. Value numbering. 2025. https://en.wikipedia.org/wiki/Value_numbering
                 [68]   GitHub. Static single-assignment form. 2025. https://codeql.github.com/docs/codeql-language-guides/codeql-library-for-go/#static-single-
                     assignment-form
                 [69]   Amazon Web Services. Potential memory leak due to slice expression. 2025. https://github.com/aws/aws-sdk-go/issues/5327
                 [70]   Rebert A, Kern C. Secure by design: Google’s perspective on memory safety. 2024. https://research.google/pubs/secure-by-design-googles-
                     perspective-on-memory-safety/
                 [71]   The MITRE Corporation. Missing release of memory after effective lifetime. 2025. https://cwe.mitre.org/data/definitions/401.html
                 [72]   Cao SC, Sun XB, Bo LL, Wu RX, Li B, Tao CQ. MVD: Memory-related vulnerability detection based on flow-sensitive graph neural
                     networks.  In:  Proc.  of  the  44th  Int’l  Conf.  on  Software  Engineering.  Pittsburgh:  ACM,  2022.  1456–1468.  [doi:  10.1145/3510003.
                     3510219]
                 [73]   Fan G, Wu RX, Shi QK, Xiao X, Zhou JG, Zhang C. SMOKE: Scalable path-sensitive memory leak detection for millions of lines of
                     code. In: Proc. of the 41st IEEE/ACM Int’l Conf. on Software Engineering (ICSE). Montreal: IEEE, 2019. 72–82. [doi: 10.1109/ICSE.
                     2019.00025]
                 [74]   Sui Y, Ye D, Xue JL. Detecting memory leaks statically with full-sparse value-flow analysis. IEEE Trans. on Software Engineering,
                     2014, 40(2): 107–122. [doi: 10.1109/TSE.2014.2302311]
                 [75]   Clang. Thread safety analysis. 2025. https://clang.llvm.org/docs/ThreadSafetyAnalysis.html
                 [76]   Chen J, Yu DJ, Hu HY. Towards an understanding of memory leak patterns: An empirical study in Python. Software Quality Journal,
                     2023, 31(4): 1303–1330. [doi: 10.1007/s11219-023-09641-5]
                 [77]   Klabnik S, Nichols C. What is ownership? 2025. https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html
                 [78]   Klabnik S, Nichols C. Validating references with lifetimes. 2025. https://doc.rust-lang.org/stable/book/ch10-03-lifetime-syntax.html
                 [79]   Qin  BQ,  Chen  YL,  Yu  ZM,  Song  LH,  Zhang  YY.  Understanding  memory  and  thread  safety  practices  and  issues  in  real-world  Rust
   255   256   257   258   259   260   261   262   263   264   265