Hi,
could someone suggest me a solution to fix the problem I mentioned in this post' title. I'm on winxp, pd-vanilla 0.43.0

Thank you very much!

does it happen EVERY time, or just with some specific patch?

if it happens every time, you'll probably have to look into playing around with your audio settings, trying different versions of pd, etc.

Hi mod!
Yes, it happens every time i turn the DSP off. I fixed it by deleting everything on my computer that had some relation with pd, including registry settings left there by pd-extended installation. After that, I "reinstalled" pd-vanilla (although it did not needed installation). I tried to avoid that whole process cause I had some arduino libraries in extra folder which needed to be collected once more. Since I am not a computer expert, it seemed the only logical solution to me.

I know that the [breakpoints] and [breakpoints~] objects can cause this, especially when processing is turned of while they're outputting values.

Anything new about this issue? Workaround, link? A recommended place for discussing bugreports?
I'm going more and more from midi to internal dsp, so this bug really touches me evil. Everytime I touch the toggle in the green dsp field, all freezes, I loose all changes after last save and have to build up my complete actual project new from this point. This happens even if I have stopped all output and closed all windows.
I'm on 64bit up to date ubuntusystems in different hardware and this issue is reproducible in all 64 bit(32bit I did not test) pd-extended and vanilla versions since 0.42.5 and ubuntu combinations.
I'd appreciate any hint

@bluesscream said:

A recommended place for discussing bugreports?

There should be a link in the help menu to file bug reports. Also, if you want to try and get a discussion going with the devs, they all hang out on the mailing list:

http://lists.puredata.info/listinfo/pd-list

Tx, posting to the list seems like a good idea