Memory leak with waveform~, poke~ and buffer~?


    Apr 03 2019 | 9:41 am
    I'm implementing a long (10s) circular buffer with buffer~, count~ and poke~, and displaying the recorded audio with waveform~ with a running cursor drawn by the line message. I've noticed on the Mac OS system monitor that Max memory keeps increasing while letting the buffer recording in a loop. The increase is slow but steady (approx 1 MB every 4 secs). If I remove the waveform~ object, memory stops increasing.
    Here's the patch:
    I'm using Max 8.0.1. Did someone experience this before? Am I missing something? thanks! jj

    • Apr 03 2019 | 8:56 pm
      not sure what causes this ... or if it is right ... but waveform has a built-in clock, which controls the GUI update. maybe at that point there is a new bug regarding mojave?
      when i am writing samples from one buffer to the other using index and poke, and have a waveform connected to the write-buffer, i dont even see the RAM usage raising during the write. and why would i; an empty buffer requires the same space than a "filled" one, and the same should be true for the waveform graphics...
      but in my case i dont use operating systems with 4x buffering nonsese...
    • Apr 05 2019 | 7:47 am
      As it turns out, it was a bug on version 8.0.1, listed here: http://cycling74.s3.amazonaws.com/support/version_8_0_4.html I updated to 8.0.4 and the memory leak is gone.