diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-06-05 20:43:39 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-06-05 20:43:39 -0700 |
commit | 0b3d456f2cba50b14664f268c100d643f3119690 (patch) | |
tree | f553e63fb4ed22a34a0daeb28f0126c7a64bce98 /ex7.mu | |
parent | b012fba1bcc37f2747b5295dd547cb6eefe5caa5 (diff) | |
download | mu-0b3d456f2cba50b14664f268c100d643f3119690.tar.gz |
clean up a large memory leak
It turns out (bowboard screen 128) on a real screen massively slowed down and ran out of memory since commit e2ab1b30b1 on May 19. The culprit was these changes, which created memory allocations for a new trace on every recursive call. I originally had some vague desire to isolate these calls from the user-visible trace. That's expensive enough that I'll wait until it becomes a concern before trying to isolate again.
Diffstat (limited to 'ex7.mu')
0 files changed, 0 insertions, 0 deletions