bcoyle
Member
I'm writing a 24/7 scheduling App. During testing, I was getting obs crashes randomly, sometimes many hours after starting. I decided to investigate by putting my program into a loop and trying to cause a crash. I knew in my program where it was stopping by looking at the log. I found that crashes were consistently happening during a obs socket command. See the crash report. The situation was that I was asking vlc or ffmpeg to load a file and quickly sending another command to see if obs was ready (my version of a sync command). With no delay, the crash happened quickly, The loop maybe running a couple hundred times. Putting in different delays, (my computers is a 4 core - hyper threaded to 8, I7,running at 3.4ghz, so fairly fast, running h264 encoding,no gpu acceleration), i found that at 40ms, still crashes but takes longer, at 50ms takes more loops and at 60ms, it would not crash, at least in the time I ran it. So, in the loop, I was sending a set source command following by another command. The 60ms time is obliviously a "TUNED" time based on my computer, and may be different for slower computers? Who knows. The source file was on a costco, 5400rpm drive, so that takes awhile. So if you are using a third party app where it can send commands, hotkeys quickly, you may want to think about delays. Obliviously, if you never have any problems, you are in good shape. This happened in my situation and may not be a general problem, but I thought I would share my experiences hoping that it might be of help to people. Maybe if other people would like to share their experiences and the solutions they found, it might start an interesting conversion.
