libcache | caching library that provides an in-memory and file | Caching library

Actually I don't know where the issue comes from but after logging out and restarting everything back on track.

The problem is that C strings are NUL-terminated, while C++ std::string can contain embedded NULs. So after reading the path, you need to shrink the string to its actual length, which is strlen(path.data()) (not path.size() which is a buffer size only at that point), before doing anything else.

So @sharkyenergy found the real bug! I am placing his solution above my suggestions:

"I developed on windows, but due to the pinch/zoom problem, i had to move to a mac. I didnt know that on mac you must add every nuget package to the .ios project too, while on windows they are shared. after adding all the packages it didnt crash anymore."

If his solution doesn't work for you, you can try the following below the line:

Things you can try,

1. While creating the archive, we use the Release-iPhone config, which is different from the Release-iPhone Simulator config. So when you are testing, you may not be testing the ACTUAL configuration. To check this, open the iOS Project Options in Visual Studio and compare all the settings to be the same (particularly the Linker behavior). Then test it on the simulator again and it could catch the error.

2. Occasionally your app can crash on launch in prod only, and the Microsoft AppCenter package can help you with this for free. Here's something you can add in the AppDelegate just when your FinishedLaunching function begins:

From the output you added, it seems there is a small issue in the environment variables you set.

For the variable PYTHONPATH, you should change the 3X part by your version of python. In your case, PYTHONPATH should point to /Applications/Webots/lib/controller/python37.

The problem here is that you are missing the correct OSX SDK to build with the conda-forge provided compilers.

You need to download the 10.9 OSX SDK from e.g. https://github.com/phracker/MacOSX-SDKs/releases and extract it onto your harddrive at e.g. /opt/MacOSX10.9.sdk. After you then have activated your conda environment set the path to this SDK using export CONDA_BUILD_SYSROOT=/opt/MacOSX10.9.sdk.

This Exception Type EXC_BAD_ACCESS (SIGSEGV) represented that we are accessing a released object

Looks like an object was deallocated yet the code assumed it was valid.

Try Zombies in Instruments . it will help to find where you sent message to released object so this crash happens.

How to use zombies in xcode ?

Your Time Machine backup of a live MongoDB database is not going to be a reliable backup, as it will not ensure that all of the individual data files are in a consistent state. It's possible that you could get very lucky and have a particular backup where the files are consistent, but not in this case.

In the future I'd suggest that you either stop MongoDB before running backup or fsyncLock().

EDIT:

As I mentioned in a comment, you might also try following this procedure to start mongod with the --repair option. It's not guaranteed to work in every case, but somewhat surprisingly it worked in this case.

A SIGSEGV is an error / signal caused by an invalid memory reference or a segmentation fault. Seems like the app is trying to access an array element out of bounds or trying to use too much memory.

The way to fix this issue is to find out what the exception may be by making it happen on another device (or simulator), or getting the full console logs from that device. An easy way to do this might be to set exception breakpoints to see where the original exception that triggered the SIGSEGV is located.