Forums > MaxMSP

pool count isn't zero

June 30, 2014 | 5:54 am


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


July 2, 2014 | 12:08 pm

Seems that I am the only one to have suffered this problem?


March 3, 2015 | 8:24 am

Having the same error. It crashes quite quickly. My patch is quite simple. Using Freenect… maybe there is the problem?

Any idea?

— Pasted Max Patch, click to expand. —
March 3, 2015 | 8:41 am

No idea on my side. Though I am not getting this particuar message any longer I am still getting the occasional full freeze, unfortunately.

Viewing 4 posts - 1 through 4 (of 4 total)

Forums > MaxMSP