Bug EXC_BAD_ACCESS errors with memory profiler

I am trying to test some issues with shader memory for addressables loading and very frequently i hit this error in xcode:

Thread 1: EXC_BAD_ACCESS (code=1, address=0x8) errors

It would often work fine and then out of no where this errors come up and the tool is unable to used forever.

The last time is when i updated my unity version to 2021.3.15f1. I tried to clean the addressables, delete the ios folder . . . but still stuck. Its particularly there for 2022.1

Any ideas?

 

Able to replicate it on a completely new project. It turns out it is linked to https://github.com/endel/NativeWebSocket
When i comment out the websocket.connect, the capture works.

ticket: https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-24860

 

Hello!
I'm getting the the same error and the app on Android works fine! I'm new to xCode do you have some tips on how to debug it.

The app starts and the crashes. I added a screenshot when I tried on the simulator.

I'm literally getting crazy, it's even an empty scene with one cube I guess is related to the libraries right?

 

thanks for narrowing it down @dan_soqqle ! and for the callstack @stamatian !
the issues seems to be related to https://forum.unity.com/threads/crashes-when-memory-profiler-capturing.1369818/ and the fix should be on the way (cc @JoshPeterson)