Lines Matching full:leaked
526 // 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>
528 // 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>
1011 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj5' is not referenced later in this execution path and has a retain count of +1</string>
1013 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj5' is not referenced later in this execution path and has a retain count of +1</string>
1142 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj6' is not referenced later in this execution path and has a retain count of +1</string>
1144 // CHECK-NEXT: <string>Object leaked: object allocated and stored into 'obj6' is not referenced later in this execution path and has a retain count of +1</string>
1532 // 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>
1534 // 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>
1833 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
1835 // CHECK-NEXT: <string>Object leaked: allocated object is not referenced later in this execution path and has a retain count of +1</string>
2005 // 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>
2007 // 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>