Home
last modified time | relevance | path

Searched refs:OOM (Results 1 – 25 of 54) sorted by relevance

123

/external/bcc/tools/
Doomkill_example.txt4 oomkill is a simple program that traces the Linux out-of-memory (OOM) killer,
5 and shows basic details on one line per OOM kill:
9 21:03:39 Triggered by PID 3297 ("ntpd"), OOM kill of PID 22516 ("perl"), 3850642 pages, loadavg: 0.…
10 21:03:48 Triggered by PID 22517 ("perl"), OOM kill of PID 22517 ("perl"), 3850642 pages, loadavg: 0…
12 The first line shows that PID 22516, with process name "perl", was OOM killed
13 when it reached 3850642 pages (usually 4 Kbytes per page). This OOM kill
17 The system log (dmesg) shows pages of details and system context about an OOM
19 changing over time. I've seen OOM kills where I wanted to know if the system
21 workload that triggered the OOM event. oomkill provides some context: at the
29 the time of the OOM kill.
[all …]
/external/llvm-project/compiler-rt/test/fuzzer/
Dfork.test10 OOM: ERROR: libFuzzer: out-of-memory
12 …%t-OutOfMemoryTest -fork=1 -ignore_ooms=0 -rss_limit_mb=128 2>&1 | FileCheck %s --check-prefix=OOM
Dfuzzer-oom.test21 sometimes, so now we accept any OOM message.
/external/perfetto/protos/perfetto/metrics/android/
Dlmk_reason_metric.proto29 // OOM score adj of the process.
41 // OOM score adj of the LMK'ed process.
Dlmk_metric.proto32 // OOM reaper kills. Enabled via the oom/mark_victim point. Should never
/external/oss-fuzz/projects/skia/
DREADME.md2 malloc_limit_mb = 500, and timeout = 10 to find actionable OOM culprits sooner.
/external/pdfium/third_party/libtiff/
DREADME.pdfium15 0028-nstrips-OOM.patch: return error for excess number of tiles/strips.
/external/igt-gpu-tools/tests/i915/
Dgem_shrink.c289 #define OOM 8 macro
308 if (flags & OOM) { in run_test()
421 { "-oom", USERPTR | OOM },
/external/dng_sdk/fuzzer/
DREADME.md24 the fuzzer to avoid frequent OOM libFuzzer crashes.
/external/ltp/runtest/
Dcrashme15 # May panic on buggy systems if the OOM killer was not fast enough :-)
/external/grpc-grpc/doc/cpp/
Dperf_notes.md20 to OOM
/external/mesa3d/.gitlab-ci/
Ddeqp-lima-skips.txt24 # Hangs / OOM
/external/scudo/standalone/
Dflags.inc48 "returning NULL in otherwise non-fatal error scenarios, eg: OOM, "
/external/kmod/
DTODO10 * Protect index against OOM
/external/llvm-project/compiler-rt/lib/scudo/standalone/
Dflags.inc48 "returning NULL in otherwise non-fatal error scenarios, eg: OOM, "
/external/perfetto/docs/data-sources/
Dmemory-counters.md224 of the app being killed. The app state can be derived in a trace from the OOM
266 [Linux kernel's OOM Killer](https://linux-mm.org/OOM_Killer).
268 user-space) and does not support tracing of Linux kernel OOM Killer events.
321 ## {#oom-adj} App states and OOM adjustment score
/external/oss-fuzz/docs/
Dfaq.md92 report this as a timeout or an OOM (out-of-memory) bug
102 We currently do not have a good way to deduplicate timeout or OOM bugs.
103 So, we report only one timeout and only one OOM bug per fuzz target.
/external/tensorflow/tensorflow/core/api_def/base_api/
Dapi_def_CombinedNonMaxSuppression.pbtxt29 classes. Note that setting this value to a large number may result in OOM error
/external/jemalloc_new/
DChangeLog76 - Refactor OOM handling in newImpl. (@wqfish)
510 - Fix various chunk leaks in OOM code paths. (@jasone)
662 + Fix irealloc_prof() to prof_alloc_rollback() on OOM.
824 - Fix OOM handling in memalign() and valloc(). A variant of this bug existed
826 - Fix an OOM-related regression in arena_tcache_fill_small(), which could
827 cause cache corruption on OOM. This regression was present in all releases
907 - Report ENOMEM rather than EINVAL if an OOM occurs during heap profiling
1165 - Fix a prof-related bug in realloc() (only triggered by OOM errors).
1258 - Add missing mutex unlocks for some OOM error paths in the heap profiling
/external/tensorflow/tensorflow/core/framework/
Ddataset_options.proto69 // use. Values greater than the available RAM in bytes may result in OOM. If
/external/oss-fuzz/docs/advanced-topics/
Dreproducing.md41 For timeout bugs, add the `-timeout=25` argument. For OOM bugs, add the
/external/jcommander/
DCHANGELOG.md149 * Fixed: OOM when parsing certain descriptions with long URL's in them
/external/libxml2/
Dxmllint.c332 OOM(void) in OOM() function
351 OOM(); in myMallocFunc()
366 OOM(); in myReallocFunc()
381 OOM(); in myStrdupFunc()
/external/libwebsockets/lib/misc/lwsac/
DREADME.md39 * Returns NULL if OOM.
/external/mesa3d/docs/relnotes/
D9.0.3.rst117 - vbo: add a null pointer check to handle OOM instead of crashing

123