I get this error message. Everything seems to work. But what does it mean? Should I fix it?

Thanks!

(Tcl) INVALID COMMAND NAME: invalid command name ".x100235de0.c"
    while executing
"$tkcanvas itemconfig $tag -text [::pdtk_text::unescape $text]"
    (procedure "pdtk_text_set" line 2)
    invoked from within
"pdtk_text_set .x100235de0.c .x100235de0.t1003abd40 {-5.08 }"
    ("uplevel" body line 4)
    invoked from within
"uplevel #0 $docmds"

@cfry Pd is composed of 2 processes: The "c" code is compiled into the main process, which handles all of the audio and message processes and some of the gui logic, and the tcl/tk/wish process which handles the actual visual interface/gui.
The 2 processes communicate by sending strings over a pipe

Whenever pd creates a new patch window, it creates a tk "canvas" object and gives it a name according to the value of the pointer for the patch. I haven't looked into how pdtk_text_set works but somehow pd is sending the tcl/tk/wish process the name of a canvas that doesn't exist on the tcl/tk/wish side

This is a bug, so if you can give steps to consistently reproduce it we should file a bug report

Hi, thanks for the reply.

I am rebuilding a pd project file quite often and it happens after a while, so I should be able to narrow it down.

I get more and more problems: Error messages in the Pd window, stuck GUI (audio running but with errors), Pd crashes, Pd crashes the computer.

Now it is at a point where it is a real problem. At some stage I slow down working on a patch just because I fear it will break, and live of course it is a nightmare.

My impression is that the gui freezing happens more frequently while using large patches with many graph on parent objects. The error messages always writes out when opening or closing a (sub) window.

I try to stay vanilla but I have some external libraries loaded. I use the pduino lib with arduino unos connected over usb.

My main computer is a MacBookPro early 2011/16 gig ram, hybrid SSD/optical drive, OSX 10.13.6 High Sierra.

But the problems are similar on other macs I use: MacBookAir 2012 with Mojave and a MacBook 2009/8 gig, SSD, with High Sierra).

So, how should I go about to report this bug? So I can help in the best way possible? Should I post the patches where the problems occur in?