[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] Re: Still occasional memory corruption...

On Nov 20, 2013 7:06 PM, "Miguel Negrão" <miguel.negrao-lists@xxxxxxxxxxxxxxxxx> wrote:
> I'm afraid I can't help much at all, but just so you feel less lonelly,
> I was at some point getting similar behaviour from sclang. At some point
> the same variable, without being changed, would output completelly
> random results.
> https://github.com/supercollider/supercollider/issues/999

This sounds related. My code is racking up some quite deep stack traces, dispatching OSC messages through multiple Protos, often by way of NotificationCenter. Proto is especially demanding on the stack, since pseudo-method dispatch through doesNotUnderstand "use"-s the Proto, incurring frames for protect and prTry. Multiple layers of notifications are involved as well. It wouldn't surprise me if the stack approached a hundred frames.

So the million dollar question is: Does anybody know enough about this to trace it in gdb and check the state of the stack? I sure don't.

> Stating the obvious, indeed one of the advantages of using a mainstream
> language is that you have people that can look into this sort of stuff
> that know exactly what is going on, freeing the sc developers to focus
> on the musical aspect of things. But then again, I'm afraid there will
> never be consensus on a language... sclang is kind of the glue that
> keeps us together, for the better or worse ;-)

I guess, it's "whose consensus." I could go with ruby, lua or Haskell (with Haskell being the least likely to gain traction among the user base as a whole).