I don’t know if this is even a sensible question, but is there anything special about a spinning-ball hang vs. Max quitting? I’m just wondering whether it might be possible to narrow down my bug search by understanding a little better what’s special about a hang. As I understand it, the spinning-ball is just OS X giving an app time to complete a task. But what is an actual hang? Is there any all-purpose answer? Are there any types of routines I should look at if the app is hanging?
okay, I think I’ve tracked it down… I assumed it must have been some of my nasty java, but it looks like it’s actually sflist~ gagging on too many preloads.
So, given that there’s no way for one to know when sflist~ has succesfully preloaded a sample, and the samples are all over my audio HD, how can I know exactly when it’s safe to attempt another preload? (hint, hint… How a bang from sflist~ when a sample is preloaded; kind of like buffer~??? mmmm… nice!)