Lines Matching full:leaked
633 // foo is not leaked, since it has been deallocated.
858 // PR 4230 - an autorelease pool is not necessarily leaked during a premature
3190 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
3192 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
3468 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
3470 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
3686 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +2</string>
3688 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +2</string>
3904 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is returned from a function whose name ('f7') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
3906 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is returned from a function whose name ('f7') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
4182 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
4184 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'date' is not referenced later in this execution path and has a retain count of +1</string>
4861 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
4863 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
5397 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
5399 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
6064 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
6066 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
6765 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
6767 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'disk' is not referenced later in this execution path and has a retain count of +1</string>
7563 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dissenter' is not referenced later in this execution path and has a retain count of +1</string>
7565 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dissenter' is not referenced later in this execution path and has a retain count of +1</string>
8492 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'session' is not referenced later in this execution path and has a retain count of +1</string>
8494 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'session' is not referenced later in this execution path and has a retain count of +1</string>
8797 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'o' is not referenced later in this execution path and has a retain count of +1</string>
8799 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'o' is not referenced later in this execution path and has a retain count of +1</string>
9789 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
9791 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
11127 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'kind' is not referenced later in this execution path and has a retain count of +1</string>
11129 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'kind' is not referenced later in this execution path and has a retain count of +1</string>
12848 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
12850 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
13085 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
13087 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'dict' is not referenced later in this execution path and has a retain count of +1</string>
13405 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13407 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13875 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('NoCopyString') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
13877 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('NoCopyString') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
14059 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('noCopyString') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
14061 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('noCopyString') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
14308 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14310 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14591 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14593 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14775 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name (':') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
14777 // CHECK-NEXT: <string>Object leaked
14884 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14886 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15027 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15029 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15170 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15172 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15298 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15300 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15392 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15394 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15486 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15488 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15580 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15582 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15674 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15676 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15986 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15988 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16080 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16082 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17095 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
17097 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
17272 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17274 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17449 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17451 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17611 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'myGradient' is not referenced later in this execution path and has a retain count of +1</string>
17613 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'myGradient' is not referenced later in this execution path and has a retain count of +1</string>
17739 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
17741 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
17867 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17869 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
17995 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'y' is not referenced later in this execution path and has a retain count of +1</string>
17997 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'y' is not referenced later in this execution path and has a retain count of +1</string>
18157 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
18159 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
18571 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str' is not referenced later in this execution path and has a retain count of +1</string>
18573 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str' is not referenced later in this execution path and has a retain count of +1</string>
18699 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str' is not referenced later in this execution path and has a retain count of +1</string>
18701 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str' is not referenced later in this execution path and has a retain count of +1</string>
18910 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str2' is not referenced later in this execution path and has a retain count of +1</string>
18912 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str2' is not referenced later in this execution path and has a retain count of +1</string>
19147 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str4' is not referenced later in this execution path and has a retain count of +1</string>
19149 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'str4' is not referenced later in this execution path and has a retain count of +1</string>
19275 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19277 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19403 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19405 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19531 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19533 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
19715 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method that is annotated as NS_RETURNS_NOT_RETAINED</string>
19717 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method that is annotated as NS_RETURNS_NOT_RETAINED</string>
20537 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('alsoReturnsRetained') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
20539 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('alsoReturnsRetained') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
20861 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('alsoReturnsRetainedAsCF') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
20863 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method whose name ('alsoReturnsRetainedAsCF') does not start with 'copy', 'mutableCopy', 'alloc' or 'new'. This violates the naming convention rules given in the Memory Management Guide for Cocoa</string>
21023 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
21025 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
21282 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
21284 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
21425 // CHECK-NEXT: <string>Object leaked
21427 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +1</string>
21734 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +2</string>
21736 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'number' is not referenced later in this execution path and has a retain count of +2</string>
22076 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'info' is not referenced later in this execution path and has a retain count of +1</string>
22078 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'info' is not referenced later in this execution path and has a retain count of +1</string>
22260 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camelcase_createno') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22262 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camelcase_createno') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22444 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camelcase_copying') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22446 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camelcase_copying') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22628 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camel_creat') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22630 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camel_creat') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22812 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camel_copymachine') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22814 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a function whose name ('camel_copymachine') does not contain 'Copy' or 'Create'. This violates the naming convention rules given in the Memory Management Guide for Core Foundation</string>
22974 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'vals' is not referenced later in this execution path and has a retain count of +1</string>
22976 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'vals' is not referenced later in this execution path and has a retain count of +1</string>
23471 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
23473 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
23682 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a2' is not referenced later in this execution path and has a retain count of +1</string>
23684 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a2' is not referenced later in this execution path and has a retain count of +1</string>
23968 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a3' is not referenced later in this execution path and has a retain count of +1</string>
23970 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a3' is not referenced later in this execution path and has a retain count of +1</string>
24179 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
24181 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
24465 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
24467 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'a' is not referenced later in this execution path and has a retain count of +1</string>
24668 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
24670 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
24886 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
24888 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
25123 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
25125 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'value' is not referenced later in this execution path and has a retain count of +1</string>
26022 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
26024 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'x' is not referenced later in this execution path and has a retain count of +1</string>
