Crash objc_retain_x0

Question

mike sldkcjnsdmhvbsdh OP

Created 1w

Replies 8

Boosts 0

Participants 2

Attaching several crash traces:

2024-02-29_22-48-33.6864_-0600-3f948243e21b4c68d77a38d9cf1cecfdfe2c1565.crash

2024-03-04_15-00-02.9335_-0600-75000cd5acd63ba1434f2ffb3648b97259dddb88.crash

2024-03-05_08-55-47.2097_-0500-f682b25663107ad46f091d65f402f2be31f3f3c6.crash

2024-03-11_08-09-00.4057_-0400-e37d1a635d51afbb67ac38b42dd79c1718a408e8.crash

2024-03-15_16-20-22.6446_-0600-d4ebccf455e8305038ca564a39a5661a1dce6231.crash

The final code:

- (NSObject*)objectAtIndex:(NSUInteger)index {
    if (index < self.count) {
        return [self.embeddedArray objectAtIndex:index];
    } else {
        [PNDErrorReporting reportError:PNDErrorReasonTypeSafeCollectionCrashPrevented message:@"Error msg"];
        return nil;
    }
}

We subclass NSMutableArray to prevent potential crashes. but we encounter a new crash in our sdk for one of the clients. Also we noticed the stack trace skipped one of the frames (stack calls) in the crash report, in which cases the stack trace wont be identical to the actual code (beside inline)?

Boost

Answer 1

DTS Engineer OP

Apple

1w

We subclass NSMutableArray to prevent potential crashes.

Say what?

we encounter a new crash in our sdk for one of the clients.

Is this the same client as in your other thread?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

mike sldkcjnsdmhvbsdh OP

1w

Subclassing Notes

Not common but defiantly possible, described in apple docs.

Yes same client :(

0

Answer 3

mike sldkcjnsdmhvbsdh OP

5d

@DTS Engineer

Any progress on that or some explanation about the crash?

0

Answer 4

DTS Engineer OP

Apple

5d

Not common but defiantly possible, described in apple docs.

Yeah, sure, but it’s a bad idea in general and a terrible idea if your goal is “to prevent potential crashes”.

Yes same client :(

OK then. IMO there’s something really broken within that app and you need to fix that before you start worrying about this.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 5

mike sldkcjnsdmhvbsdh OP

5d

@DTS Engineer

but could you please explain the crashes?

0

Answer 6

DTS Engineer OP

Apple

5d

The immediate cause of these crashes is that you’ve passed a bogus object to objc_retain_x0 (a specialised form of objc_retain used on Apple silicon). You’re doing this from your array subclass, so there are two potential causes:

There’s a bug in your array subclass.
The process’s state is corrupted such that your legitimate code is crashing.

Regarding the first, IMO you shouldn’t have this array subclass in the first place, so I’m not inclined to go looking for bugs in it.

Regarding the second, we know from your other thread that this process’s state is corrupted because it’s causing other code to crash.

My advice is that your remove your array subclass and then hunt your memory corruption issue (well, your client’s memory corruption issue).

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 7

mike sldkcjnsdmhvbsdh OP

4d

@DTS Engineer

both crashes occurs in 2 different places under 2 different threads.

The current one is related to the processing of the payload we received from the BE and runs in sync queue.

While the previous crash runs and different sync queue and its purpose is to handle app analytics as soon as one is received.

With that to say its hard for me to directly link between the two issues except of some general memory corruption

0

Answer 8

DTS Engineer OP

Apple

3d

With that to say its hard for me to directly link between the two issues except of some general memory corruption

Well, yes, that’s exactly the point I’m making. AFAICT the crash on that other thread can only occur due to a memory corruption issue. Given that the crash on this thread only occurs when your SDK is integrated into the same client, my theory is that the same underlying memory corruption is causing both problems.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0