oh, thanks for the comprising debug info...
yes, the first error might not be crucial...
i think i tracked down the reason, its due to some new code-inline-image feature i'm currently testing. some lines too long in the shader code - firefox doesn't seem to like that... i'm on it...
and the socket stuff is for remote osc-connections (you'd have to start a small server-script locally to use that - see shaderoo help-page)
Edit: now that I think about it, just because shaderoo.js is loaded first, doesn't mean getDataFromText will by called immediately. I don't have the time to debug or even just read someone else's code right now, so I'll just leave it at that.
The second:
Alas Firefox is failing to tell me where exactly in the code the error is coming from.I also see this warning:
That's true, I'm not hosting anything on http://127.0.0.1:8081 :eyeroll: