Qingtian
Qingtian
@greggirwin According to the documents, yes. I pointed it out as I don't see a code branch to handle this case. The `get?` parameter in `interpreter/eval-path` should be used for...
No crash anymore.
> Now I modify the test a little bit and: > > ``` > Red [] > > ; recycle/off > ; hash!: block! > loop 5000 [ > object...
No error if just `copy r`.
I think it's caused by OS resources cannot be freed by the GC. A weird workaround: ``` r: rtd-layout ["abc"] view [ box rate 99 on-time [ loop 999 [face/draw:...
Looks like even a simple `on-time` event keeps using memory. ``` view [ base 500x300 rate 99 on-time [ probe stats ] ] ```
> Yes but just a bit, and if you add `recycle`, it's stable. Yes. But you have to do `recycle` manually, it should be triggered automatically.
It doesn't get triggered even waiting a few hours. But it's another small issue. I fixed the big memory jump issue. Pushing it now.
It still has an issue which the execution time keep increasing until the GC get triggered. It because the algorithm used in the hashtable does not suit well with the...
The drawing is slow because the ownership system takes too much time. When doing `face/draw: drawn`, all the values in the `face/draw` block will be deleted from the ownership system,...