Is there a limit on the number of objects tracked by the poly spatial trackers?

I did a test where I instantiated 4000 cubes at the same location. When running on device, if I look at those cubes, the entire OS crashes. I did another test with 1200 images and it crashes in a similar way. The crash can also happen with a lower number of objects but it takes a bit longer. Everything seems to work fine in editor and simulator though.

There is no hard limit to what the trackers handle explicitly. I can’t tell from your post why you think it’s the trackers directly that are an issue. Do you have a crash stack that points there?

Maybe it’s not directly related to the trackers. I probably thought that because it was happening for components with an associated tracker.

When I disabled the MeshRendererTracker it was fine, but it makes the objects not show up so you can’t actually look at them to cause the crash.

I don’t think I can get any sort of crash stack since it completely crashes the OS and stops running the app in Xcode. Not sure if this will help, but I see this in the console logs when the crash happens:

apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
Failed to commit transaction (client=0x1e2dc8ed) [0x10000003 (ipc/send) invalid destination port]
[C:3] Error received: Connection interrupted.
[C:3-1] Error received: Connection interrupted.
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
Failed to commit transaction (client=0xe41e09bc) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_read_request_report [C1] Receive failed with error "No message available on STREAM"
nw_protocol_socket_reset_linger [C1:2] setsockopt SO_LINGER failed [22: Invalid argument]
apply fence tx failed (client=0x3597b577) [0x10000003 (ipc/send) invalid destination port]
Message from debugger: Terminated due to signal 9

Please file a bug with a repro project and post the ID here.

Thank you.

I just filed a bug report. Its ID is IN-58784.

Thank you, we’ll get on it as soon as possible.

1 Like

As this is an OS crash, it’s something you’ll need to file with Apple – please use the Feedback Assistant to send in information to them (they all get read and triaged!). But this is something that’s known and is a limitation of the OS. I don’t know what the hard limits are, though, and I believe the limits are per-frame (i.e. instantiating a few hundred every frame up to 5k total may work where instantiating 5k at once won’t).

Thanks @v_vuk , I’ll file a report with Apple. Do you know the name of the native class that’s being used by the PolySpatial package and is causing the crash?