High Rtrace values causing test errors?

Hello! This might be more of a discussion point, than a bug in as-pect. I’m not too sure, but I’ll create a repro case if you think this might be a bug 😄

So I’m working on a unit test of an object with a complex constructor. I’m testing a case I expect to throw, and at the end of the test I get: RTrace: +16. And this was causing a really weird behavior, where the test would fail, which appeared to be a runtime error. And as-pect would also output:

---

And for geenral google and github search:

[Error]: rtrace: Block: 8940 => shadow region mismatch: 0 != 8940
 [Stack]:     at Rtrace.unmarkShadow

...

---

So I’m not too sure what this means, but looking at the docs for RTrace, it meantions is might be a memory leak? https://tenner-joshua.gitbook.io/as-pect/as-api/rtrace-and-memory-leaks

However, the constructor is definitely creating a lot of objects on the runtime, and even runs through a few loops. If I understand the docs correctly, the Rtrace is a report of the number of object that were alive when the function had an error. So, a high Rtrace value (if it’s not being cleaned up like the docs mentions), makes sense for this test.

To fix this in the meantime, I just threw the problematic test, as the last test in my describe block, and everything seems to be working fine now 😄

Is this something on me? Or is this an as-pect issue? 🤔

[jtenner]

This should be all set.

[jtenner]

This is why I’ve waited on development. I’m very excited for the new release.