Pduino has nothing to do with [serial_print]. Such a scenario could suggest some problem with Pd when sending data to [comport] and processing data received from it (I'm not suggesting it's a problem with [comport] since disconnecting it from [serial_print] solved the crash problem). I haven't checked your files yet (see my previous reply asking for them via a different medium), so I have no idea what could be wrong with [serial_print]. I'll get back once I have your files and have checked them.

Thank you for doing this. It may also be relevant that I experienced the exact same of freeze/crash behavior when using Pduino.

Date: Fri, 9 Apr 2021 17:14:18 +0300
From: Alexandros <adrcki@gmail.com>
To: pd-list@lists.iem.at
... 
This has to do with the abstraction I made then. We did discuss about it
on Pd's forum, but it didn't occur to me that this could be the case.
I'll have a look at it and get back to you.

On 9/4/21 5:10 ?.?., Nicklas Lundberg wrote:
> Hmm, it does not crash when [serial_print any] is disconnected. You
> can quit normally.
>
> This may be relevant:
>
> Pd console reports no errors when communication fails when trying too
> fast updates (with [serial_print any] disconnected less than 30 ms).
>
> I uploaded a similar setup (pd patch+arduino sketch) to the folder.
> Here it does not crash even if updates are sent every 1 ms. And the pd
> console starts to write error messages when the communication is too
> fast (starts around 7 ms).

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list