Lines Matching full:leak
168 ErrorLeak, // A memory leak due to excessive reference counts.
169 ErrorLeakReturned, // A memory leak due to the returning method not having
1685 class Leak : public CFRefBug {
1687 Leak(StringRef name)
2141 // the leak. The function can also return a location context, which should be
2210 // If we are reporting a leak of the object that was allocated with alloc,
2221 // If allocation happened in a function different from the leak node context,
2250 // We are reporting a leak. Walk up the graph to get to the first node where
2261 // Compute an actual location for the leak. Sometimes a leak doesn't
2377 os << "Potential leak ";
2429 /// Optional setting to indicate if leak reports should include
2482 leakWithinFunctionGC.reset(new Leak("Leak of object when using "
2488 leakWithinFunction.reset(new Leak("Leak of object when not using "
2492 leakWithinFunction.reset(new Leak("Leak"));
2502 leakAtReturnGC.reset(new Leak("Leak of returned object when using "
2508 leakAtReturn.reset(new Leak("Leak of returned object when not using "
2512 leakAtReturn.reset(new Leak("Leak of returned object"));
3355 // a leak (as the caller expects a GC'ed object) because no
3610 // Generate an intermediate node representing the leak point.
