You are reading a single comment by @Raik and its replies. Click here to read the full conversation.
  • Great - glad it's helpful! The graph vis is - I tried this a while ago (you can see E.debugVariables got added a long while back) but never found something that would visualise it properly before.

    The complaints about Recorder using a bunch of RAM got me to try it again, and as it happens I spotted some ways the interpreter could save some memory, so firmwares from the last day should be a bit more frugal.

    @Raik that's cool. What you're seeing there is a bunch of JS arrays (one var per index element). You can see they're all referenced from one point (another array?) which it itself referenced from ROOT (you can see the red line).

    Not sure what clock face you have, but it's possible that it could be using a Typed Array instead, which wouldn't need all the index vars so could save a decent amount of memory.

    I guess these sorts of things would be good in the README to give an idea about what to look for

  • Not sure what clock face you have

    I'm using the Numerals. Ah, those plumes originated from the numerals polygon definition then.

    var numerals = {

    I'll see how I could be rewriting this.


Avatar for Raik @Raik started