iOS18Crach xzm_xzone_malloc_tiny_outlined

Question

Created Sep ’24

Replies 4

Boosts 0

Views 1.3k

Participants 4

We have found a large number of memory-related crashes in iOS18, and multiple issues have finally pointed to this crash line xzm_xzone_malloc_tiny_outlined. Do not know how to solve it now

Answered by DTS Engineer in 805063022

On Apple platforms, malloc is backed by a variety of zones. Indeed, it’s possible to create your own zones using the API in <malloc/malloc.h>. To do this you have to create a zone allocator function.

xzm_xzone_malloc_tiny_outlined is part of one of the built-in zone allocator functions. If it’s crashing, it’s very likely that this is because of a memory management bug. I recommend that you start your investigation by deploying the standard memory debugging tools.

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

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’24

Recommended

On Apple platforms, malloc is backed by a variety of zones. Indeed, it’s possible to create your own zones using the API in <malloc/malloc.h>. To do this you have to create a zone allocator function.

xzm_xzone_malloc_tiny_outlined is part of one of the built-in zone allocator functions. If it’s crashing, it’s very likely that this is because of a memory management bug. I recommend that you start your investigation by deploying the standard memory debugging tools.

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

1

Answer 2

bbLevenDev OP

Mar ’25

@Murphy_mao Hello, I have the same problem. I used the leak check of instruments and found no memory leak. Could you please tell me what your C language leak is like?

0

Answer 3

nikolayfromlondon OP

May ’25

I got the same crash in 18.4.x. Reported to Apple - FB17347956

0

Answer 4

DTS Engineer OP

Apple

May ’25

Folks, lemme reiterate the advice I gave to Murphy_mao: This is almost certainly a memory management bug within your process. It’s possible that the bug is in an Apple framework, but it’s most likely to be a latent bug in code you control that just happens to be exposed by an unrelated change in iOS 18.4. Either way, the best path forward is to try to isolate the bug with the standard memory debugging tools.

While you’re free to file a compatibility bug against iOS 18.4, its unlikely to get traction unless you include crystal clear evidence that the problem lies within the OS itself.

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

0