I have a Unity piece installed in a show that should theoretically run endlessly for a few weeks. I developed it on Windows using Unity Pro and then built an .app in order to put the project on the iMac that is in the show. Unfortunately, the project becomes unresponsive after some period of time. I’m trying to nail down the exact time frame, but it is likely something like 4-12 hours before it becomes unresponsive. (edit: I should clarify - it doesn’t crash, just becomes completely unresponsive.) I’m at a bit of a loss as to how to find what is causing the freezing.
The iMac is set to never go to sleep, to never turn off the display and to never shut down the hard drive.
The code for the project doesn’t contain any objects that are generated during runtime (other than PlayOneShot AudioSources). I use PerlinNoise often, so I get Time.time and multiply it by a small scaler value (< 2) before passing it to PerlinNoise, but those values should be far from exceeding the max size of a float. There are constantly looping sounds, but I used the profiler and watched the memory usage for about 10 minutes - nothing increased.
Does anyone have any thoughts for how to nail down what is going haywire here?
may be a ram issue, something adding up in that time frame, i use a free app from the mac app store called super memory cleaner, that gives you a ram meter in the menu bar, you could have that running over some time and see if the memory runs out after some time, and then with the activity monitor watch which is the offending application, it may not be your app at all