Scratch

I'll work on doing that, but I don't think its strictly necessary: I can generate tons of these messages by simply opening Scratch and moving the mouse around over the application. In this case there's no script running, and only the initial sprite loaded.

I've got a console window open running

   tail -f /var/log/system.log

which allows me to visually correlate these errors with actions in the application - I haven't found anything that doesn't produce errors. That is, each movement of the cursor from button to button or pane to pane generates dozens of these.

Of the (by now) nearly 10M lines of this stuff in system.log, nearly all are the kinds I've already described. It occurs to me the 39 lines that are different might be more interesting - signal to noise and all that.

So, of those 39 lines,

3 look like this:

Sep  6 16:21:41 oxygen [0x0-0x24f84f6].org.mozilla.firefox[0]: Sat Sep 06 16:21:41 PDT 2008 JEP creating applet ScratchApplet (http://scratch.mit.edu/static/misc/)

27 look like this:

Sep  6 16:25:14 oxygen Scratch[26545]: *** _NSAutoreleaseNoPool(): Object 0x10a460 of class NSPathStore2 autoreleased with no pool in place - just leaking\nStack: (0x904bccdf 0x903ca767 0x903f0831 0x36c22)

and 9 look like this:

Sep  6 16:28:39 oxygen Scratch[26591]: *** _NSAutoreleaseNoPool(): Object 0x1094f0 of class NSCFString autoreleased with no pool in place - just leaking\nStack: (0x904bccdf 0x903c9562 0x903d1dde 0x903ed90a 0x903f086b 0x903c9a0a 0x903f07ee 0x36c22)

Hope this helps.

I don't know enough about Squeak to know where to start looking. I did try running the scratch.image under the 3.8.19betaU squeak release, and it worked without throwing the log events. I didn't find a good way to quit - quitting squeak does nothing, apparently - I had to reach for "force quit". So, clearly it's not a replacement, but maybe a useful datapoint.

Did I mention I really like the list feature and don't want to go back to 1.2.1?

Is there anything else I can do for diagnosis?

tia

ross

Last edited by randrus (2008-09-08 10:03:50)

So, I did try some of those things.

I don't see the problem at all under 1.2.1. The same script won't run because it uses some 1.3-specific features, but ... I don't even have to run a script at all - I can generate the errors by starting Scratch and simply moving the mouse.

I did download a different squeak vm and the problem does not occur, but there seem to be other issues - like I couldn't quit Scratch 

But the broader hint I think is to look beyond Scratch proper. I poked around a little trying to figure out which build of Squeak is included w/ Scratch - it's not obvious - but perhaps I should focus there.

Thanks for the ideas...

ross

Thanks - didn't know that trick.

r

Hi, randrus.

Thanks for reporting this problem. I had seen the occasional warning in the log, but I thought they were pretty harmless. We'll look into it.

    -- John

FWIW I upgraded to OSX 10.5.5 and it does not help.

ross

I was wondering if there was something about my script that was causing the problem - it uses the new "list" mechanism to play an animation loop.

But it turns out I don't need to do anything tricky to see the problem: running the following script with the default "Scratch" sprite and the messages are streaming into syslog without any further mouse or keyboard interaction.

[blocks]

<forever>
<glide(1 )secs to x   100 )y   100
<glide(1 )secs to x   -100 )y   -100

[/blocks]

ross

Last edited by randrus (2008-09-18 09:15:31)

Downloaded and verified!

Thank you VERY much!

ross