Debugging (IOAF code 11) and (IOAF code 4) errors.

Question

ForeverTangent OP

Created Jan ’21

Replies 1

Boosts 0

Views 3k

Participants 3

I have some Metal Code, that goes along fine and then my app starts throwing the following errors.

Execution of the command buffer was aborted due to an error during execution. Caused GPU Address Fault Error (IOAF code 11)

and then...

Execution of the command buffer was aborted due to an error during execution. Ignored (for causing prior/excessive GPU errors) (IOAF code 4)

I am guessing the prior causes the later, but I can't figure out what is causing the first exactly.

Is it possible to set up a Symbolic Break Point or something to catch these types of errors? Right now I feel like I am grasping in the dark to figure out what is going wrong in my code.

Thanks

Stan

Boost

Answer 1

Graphics and Games Engineer OP

Apple

Jan ’21

As you suggest, the second is most likely the result of too many invocations of the first error.

The first error suggests that your kernel/shader is writing to out-of-bounds memory. You should enable "Shader Validation" in the scheme's Diagnostics tab. This will perform bounds checking an hopefully root out where your kernel is faulting.

2