Home
last modified time | relevance | path

Searched refs:leaked (Results 1 – 10 of 10) sorted by relevance

/f-stack/app/redis-5.0.5/deps/jemalloc/msvc/test_threads/
H A Dtest_threads.cpp81 size_t leaked = allocated2 - allocated1; in test_threads() local
82 printf("\nDone. Leaked: %zd bytes\n", leaked); in test_threads()
83 …bool failed = leaked > 65536; // in case C++ runtime allocated something (e.g. iostream locale or … in test_threads()
/f-stack/freebsd/contrib/openzfs/config/
H A Dkernel-kmem.m45 dnl # if memory was leaked.
33 dnl # alloc and free. When the SPL module is unloaded a list of all leaked
H A Dzfs-build.m4101 dnl # Then at module unload time if any bytes were leaked it will be reported
129 dnl # kmem_free(). When the module is unloaded a list of all leaked addresses
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_get/
H A Dzpool_get_parsable.cfg33 "leaked" "size")
H A Dzpool_get.cfg57 "leaked"
/f-stack/dpdk/doc/guides/contributing/
H A Dvulnerability.rst234 If the issue is leaked during the embargo, the same procedure is followed
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/perf/
H A Dperf.shlib296 # In case there's been some "leaked" zinject delays, or if the
/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_18_02.rst51 releases these resources, ensuring that no hugepage memory is leaked. It is
/f-stack/app/redis-5.0.5/deps/jemalloc/
H A DChangeLog986 + Internal reallocation of the quarantined object array leaked the old
1336 to be leaked during thread exit.
1373 - Fix a chunk leak. The leaked chunks were never touched, so this impacted
/f-stack/freebsd/contrib/dev/acpica/
H A Dchanges.txt8472 could be leaked for each block of executed module-level code if the
8618 operand object was leaked. Lin Ming.
15259 leaked under certain error conditions.