This is another issue I think is new to Sequoia. I have a console app that is supposed to run 24/7, but after a bit the app gets no CPU time at all. It shows 0.0% in activity monitor, when it would normally show around 30%, and during debug the IDE cannot interact with it at all. Meaning I can’t stop or pause it. BUT if I press Ctrl+C my signal catch code does fire with a StackOverflowException at the Function line. So I suspect that exception is elsewhere. The app is not using any of the new features such as preemptive threads. Actually it’s still using 2023r3. I’ve not seen this issue until recently, which makes me believe it’s Sequoia-related. But I’m not certain, and it makes me hesitant to upload it to production.
Anybody seen something like this? In all my years, I can’t recall a situation where all threads just stop. Not error, just… don’t get time.
I suspect that StackOverflowException is related somehow. My unhandled exception event does not fire, nor any of my other exception handlers. I have not disabled stack checking.
1 post - 1 participant