Lines Matching full:leaked
659 // foo is not leaked, since it has been deallocated.
884 // PR 4230 - an autorelease pool is not necessarily leaked during a premature
3252 // 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>
3254 // 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>
3496 // 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>
3498 // 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>
3680 // 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>
3682 // 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>
3864 // 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>
3866 // 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>
4108 // 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>
4110 // 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>
4787 // 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>
4789 // 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>
5255 // 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>
5257 // 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>
5854 // 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>
5856 // 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>
6521 // 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>
6523 // CHECK-NEXT: <string>Object leaked
7319 // 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>
7321 // 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>
8180 // 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>
8182 // 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>
8417 // 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>
8419 // 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>
9307 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
9309 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
10577 // 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>
10579 // 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>
12230 // 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>
12232 // 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>
12501 // 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>
12503 // 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>
12787 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
12789 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13087 // 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>
13089 // 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>
13203 // 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>
13205 // 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>
13418 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13420 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13667 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13669 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13783 // 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>
13785 // 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>
13892 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
13894 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14069 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14071 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14246 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14248 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14374 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14376 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14468 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14470 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14562 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14564 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14656 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14658 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14750 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
14752 // CHECK-NEXT: <string>Object leaked
15028 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15030 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15122 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15124 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
15967 // 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>
15969 // 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>
16144 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16146 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16321 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16323 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16517 // 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>
16519 leaked: object allocated and stored into 'myGradient' is not referenced later in this execution path and has a retain count of +1</string>
16611 // 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>
16613 // 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>
16739 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16741 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
16833 // 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>
16835 // 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>
16961 // 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>
16963 // 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>
17341 // 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>
17343 // 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>
17435 // 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>
17437 // 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>
17612 // 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>
17614 // 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>
17849 // 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>
17851 // 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>
17943 // 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>
17945 // 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>
18037 // 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>
18039 // 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>
18165 // 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>
18167 // 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>
18281 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method that is annotated as NS_RETURNS_NOT_RETAINED</string>
18283 // CHECK-NEXT: <string>Object leaked: allocated object is returned from a method that is annotated as NS_RETURNS_NOT_RETAINED</string>
19069 // 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>
19071 // 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>
19359 // 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>
19361 // 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>
19487 // 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>
19489 // 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>
19712 // 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>
19714 // 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>
19821 // 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>
19823 // 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>
20096 // 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>
20098 // 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>
20418 // 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>
20420 // 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>
20534 // 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>
20536 // 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>
20650 // CHECK-NEXT: <string>Object leaked
20652 // 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>
20766 // 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>
20768 // 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>
20882 // 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>
20884 // 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>
21010 // 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>
21012 // 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>
21405 // 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>
21407 // 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>
21616 // 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>
21618 // 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>
22004 // 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>
22006 // 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>
22351 // 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>
22353 // 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>
22875 // 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>
22877 // 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>
23112 // 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>
23114 // 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>
23330 // 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>
23332 // 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>
23601 // 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>
23603 // 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>
24330 // 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>
24332 // 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>
24424 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj' is not referenced later in this execution path and has a retain count of +1</string>
24426 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj' is not referenced later in this execution path and has a retain count of +1</string>
24845 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
24847 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
25750 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj' is not referenced later in this execution path and has a retain count of +1</string>
25752 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj' is not referenced later in this execution path and has a retain count of +1</string>
25994 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'arr' is not referenced later in this execution path and has a retain count of +1</string>
25996 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'arr' is not referenced later in this execution path and has a retain count of +1</string>
