Hi,

I am working on a patch that use Gem, twitter request using Python, and sound.
(pd-extended 0.43.4, OSX 10.9)

Everything works smoothly but suddenly, I get some weird Tcl error printed in red (It points me to some basic objects like trigger, list, inlet, list split... inside list-filter or list-drip abstraction that proceed long lists).
Not long time after, the program close.

Can somebody explain me why, and what I can do? Maybe using Vanilla could be more stable ? (Then I'll need to work again on it as I use a lot externals).
Thanks!

Tcl error example:

(Tcl) ERREUR NON GÉRÉE : extra characters after close-brace
    while executing
"::pdwindow::logpost {.xac4a5e0} 1 {stack overflow}::pdwindow::post {
}
�hael/Desktop/Projects/Corps_R::pdwindow::post {
}
�blur.vert
}
::pdwind::pdw..."
    ("uplevel" body line 123)
    invoked from within
"uplevel #0 $cmds_from_pd"stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
stack overflow
(Tcl) NOM DE COMMANDE INVALIDE : invalid command name "::logpost"
    while executing
"::logpost {.x4cc0e0} 1 {stack overflow}"
    ("uplevel" body line 31)
    invoked from within
"uplevel #0 $cmds_from_pd"

@60htz I think it likely that you have a stack overflow caused by a data feedback loop...... somewhere in your patch.
If you post the patch then vanilla / extended /osx / Linux / Windows ........ questions can be eliminated, and someone might find the error......
David.

Thanks,
Here is a piece of my patch to have a look...
I need to remove strange character (sometimes [text3d] don't like), and I want to remove url from tweet...

I have up to 20 tweets that comes at the same time for parsing, maybe that's why some list-filter don't like it? Is there another way to do such a thing?

twitter_parsing_pb.pd

I also have those error:

(Tcl) ABSENCE DE L'ACCOLADE DE FIN '}' : missing close-brace
    while executing
"�:pdwindow::logpost {::pdwindow::logpost {.x2485b0} 1 {stack overflow}
::pdwindow::post {
}
::pdwindow::logpost {.x2485b0} 1 {stack overflow}
::pdwin..."
    ("uplevel" body line 1258)
    invoked from within
"uplevel #0 $cmds_from_pd"stack overflow

@60htz No errors at all with that patch on my system (Windows7 Pd-extended 0.43.4)...
I clicked the message and the message in the "parse" sub-patch. Slightly different output but no errors for either. It is quite happy taking in the message 100 times per second.
David.

Yeah, thats the problem... when I receive data from twitter, suddenly after 5min the list-filter abstraction have many errors.

Then pd hangs. I guess there is still many serious bugs inside pd-extended?

@60htz It's an unknown............. is it possible to know which message (or message form) causes this stack overflow. It seems that in "normal" circumstances there are "no problems"...... ?
I am running a test..... your message...... 100 times per second....... until I get bored (after dinner)....
I will let you know.

Well.... your patch has processed that particular message (tweet) 100 times per second for the last 50 minutes without any problem........
You could maybe write the tweets to a log file (from Pd so that the last tweet in the file is the culprit) and so find find the character sequence that is responsible......
David.

Thanks for the help whale-av
I tried to log the file that made an error, and then process it in the parsing abstraction.
No problem occurs...

I really think the problem is related to a buggy object somewhere, as my last "stack overflow" pointed me to a glsl_vertex object... or maybe it's a bug in the tracking system that mess with object id? I am fed up with those bugs in extended.

I am using the qweb twitter patch that uses Python script also, and remember always having surch a problem... if anybody use it and tell me that it's working in pd vanilla I would be happy to hear it!

Also my exhibition is mid december in Taiwan so I hope I will find a way to fix it!

@60htz GL tools (such as glsl_vertex) in gem are not part of vanilla........ Vanilla is pretty basic...... audio and midi...... no video, no osc, no physical modelling.....!
I have tried your patch (twitter-parsing.pd the bit that you posted), with random characters. It throws errors with a semi-colon (;) which I would expect as it is a special character in Pd. That makes me wonder whether your feeds are trying (a big word...... not trying, but) just happen to be sending messages to Pd in error, and Pd is trying to execute / interpret them?
For the qweb software you could try sending an email to the author......... there is a contact address on the Pd site.........https://puredata.info/downloads/Qweb
David.
PS...... a semi-colon sends the message that follows (until the next white space) directly from the message box to the Pd program....... you don't need to connect the message box to anything for this to happen!

I did a test for 20min just half an hour agoo and I just ended by removing that semi-colon accidentally... and I think you guessed right!

I finally understand why the error was from a different objet every time... it just tried to send a tweet to that object if the second word matched and sometimes even to pd itself trigerring weird tcl errors.

Thanks a lot David to make it clear to me

@60htz You are welcome......... I hope that is really the problem solved and you are more or less on your way to Taiwan!!
David.

Finally the problem is still here... I tried to add filter for ASCII character "59" but still have the problem...

Can you tell me how you did the test ?

@60htz Hello again......... I had just typed like a maniac into the message box at the top of your patch...... hitting all of my keyboard keys at random..... and then clicked that message.
I then saw that Pd terminal showed errors, and they were always "words" that were preceded by a semi-colon in the message.
But I think that you need to remove the semi-colons before they arrive in the Pd. patch. I have not tried the qweb patch...... the website seems to have been hacked. Once the semi-colon is in a Pd message it is too late..... it will try to open an object with the name of the characters that follow, and in a worst case scenario it will actually (if you are very unlucky) open a real object!
David.

The problem is that if I try to remove the semi colon, it still trigger the random tcl error...

Now I made a one hour test using pd vanilla and same twitter feeds, and I have no errors at all !

So I guess the final solution is to use vanilla and maybe compile some missing lib, too bad that OSX have no pre-compiled external using Deken plugin!

Thanks for your help