pool count isn't zero

Lars Graugaard's icon

Hi,

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

Thanks!
Lars

Lars Graugaard's icon

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

Lars

Julien-Robert's icon

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

Max Patch
Copy patch and select New From Clipboard in Max.

Any idea?

Lars Graugaard's icon

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

Jean-Francois Charles's icon

Hi there, I'm bumping this question: would anybody know more about the reason this message is printed to the Max Window?
I get, for instance (on Mac):
"our pool count isn’t zero (7), must be calling from the wrong thread…living dangerously"
"our pool count isn’t zero (-5), must be calling from the wrong thread…living dangerously"
Indeed, dangerous: a Max crash is coming.
Thanks.

Cora Lee's icon

Same question

Tale Twist's icon

Same problem here.

Sabina's icon

I have the same problem, not idea what is going on yet??

Isandro Ojeda-García's icon

Same problem here... :-/

Isandro Ojeda-García's icon

Hey there, had somebody some info? I'm becoming crazy with this problem... -_-

Rob Ramirez's icon

we have no way of offering help without seeing a patch that reproduces the issue. My recommendation is to send directly to support with all system info and applications settings