[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] SystemClock bug?
Sorry, didn't read your example closely enough. Maybe
it is a queue size thing.
What happens if you schedule the 100 random number
posts within 20 seconds rather than 4?
--- James Harkins <jamshark70@xxxxxxxxx> wrote:
> I have found repeatedly that scheduling too many
> events to fire too quickly reliably causes the
> language to crash. I don't believe it has to do with
> scheduling size restriction, but rather with the
> number of functions that are executing
> You can get the same crash by scheduling complex
> functions so quickly that the execution overlaps by
> high amount. If a function takes 0.1 seconds to
> its result and you schedule the function to execute
> 200 times with 0.001 seconds between onsets, down
> I don't see it as a bug, just a reasonable
> This kind of scheduling could probably be made
> but that might have a negative impact on performance
> H. James
> --- nikolai collinsky <nikolaicollinsky@xxxxxxxxxxx>
> > //this crashes SC3-
> > scheduling queue size restriction?
> > (can get round by converting absolute scheduling
> > delta time scheduling to use less clocks but
> > would be nice to have safe scheduling
> > possibilities...)
> ____ James Harkins /// dewdrop world
> \ / jamshark70@xxxxxxxxx
> \/ http://www.duke.edu/~jharkins
> "... love and hot pants, peace, harmony..."
> -- Dick Lee, Hot Pants: The Musical
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> sc-dev mailing list
____ James Harkins /// dewdrop world
\ / jamshark70@xxxxxxxxx
"... love and hot pants, peace, harmony..."
-- Dick Lee, Hot Pants: The Musical
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.