pool count isn't zero
Jun 30 2014 | 12:54 pm
Recently I have been getting variations on this error message, followed within 5-15 minutes by a violent crash:
"our pool count isn't zero (7), must be calling from the wrong thread...living dangerously"
What thread are we talking about? Working on a large patch on a single-core machine I am using a couple of poly~ objects but without the parallel processing option set.
It may obviously be my code though I am not that certain what it can be. And re-installing max did not solve the issue. But before I pick the code apart to identify the culprit I wanted to hear the opinion of the forum. There are two forum topics that give mention to pool count, but none pertaining this issue.
I am on a MacBook Pro 2,3 GHz Intel Core i7, OSX 10.9.3, max 6.1.7