Thread stack region size is quite large than usual

Question

Created Apr ’24

Replies 2

Boosts 0

Participants 2

After enabling the signal alternative stack using sigaltstack, the thread stack region size comes to be 128 MB. The stack region size is only 8 MB without enabling the signal alternative stack. (get by calling the mach_vm_region_recurse function)

It only happens on macOS 14 or later, and M series silicon.

The growth of the stack region size results in a too-large minidump file when we generate a crash report using Google's crashpad library.

Could anybody tell me why the size has increased so much? And is there a way to work around it?

Boost

Answer 1

dailongchen OP

Apr ’24

I created a DTS ticket for it, but don't know how to track its status.

0

Answer 2

DTS Engineer OP

Apple

Apr ’24

I created a DTS ticket for it

OK.

but don't know how to track its status.

Sadly, there’s no way to do that. DTS TSIs are all handled by email.

We’ll reply via your TSI shortly but I want highlight this bit:

The growth of the stack region size results in a too-large minidump file when we generate a crash report using Google's crashpad library.

DTS doesn’t support the development of third-party crash reporters. For more background as to why, see Implementing Your Own Crash Reporter. Does setting sigaltstack cause problems for the Apple crash reporter?

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

0