Hi,

I had been using an Raspberry Pi 4 with 4 gigs of Ram for 3 or 4 months and it was working really great. One thing I noticed about it, which was different from every other Pi i've used was it seemed like it was doing multi-threading on it's own.

I would put " htop" in the terminal and I could see the different processors workload changing, increasing, decreasing, etc.

I upgraded to a Pi 4 with 8 gigs of Ram. One of the Pure Data pieces I was able to play pretty easily on the other pi with 4 gigs I am having a hard time doing on the Pi that is 8 gigs of Ram. I ran htop in the terminal and I was surprised that it's not multi threading. I had one processor doing almost all the work, and I am getting Stack Overflow in the Pd terminal, and the audio will sound crappy and just cut out sometimes.

My question is should I increase the buffer size? Will this make it less likely to have a stack overflow?

Also, is there some setting I need to do to get the multi threading that I don't know about?

Thank you for the help in advance.

By the way, I accidentally corrupted my Pi 4, 4 gigs of ram disc image so I can't go back and look at it. I know, stupid mistake.

@nicnut Can not answer to the multi-threading question, but stack overflow basically means that a computation is passing the same Pd object too often within a loop. You can break the loop by putting [del 0] in it, but it most of the times means that there is some error in the program.

@ingox Thanks for the explanations. I think that helps.

I think something is just wrong with this particular patch. I opened a few other patches and they worked ok and did do multi threading.

This one particular patch doesn't and it also has stack overflow problems. I have a feeling it's because it has stuff from older librairies when I made it and it's using newer libraries now, so things are a little messed up.

Anyway, I'm gonna say this one is solved and just trash this patch , or update it.

thanks, Nick

@nicnut You can try to use "Find last error" to at least pin down the source of the stack overflow a little bit, but in my experience this is may sometimes be confusing as any object within the loop in question can report the stack overflow. But should show the area within the patch.

OK thanks @ingox, that's helpful. I was thinking of deleting parts of the patch till I isolated it, but I'll try your method first.