I made a test and ensuring the queue.stop(); queue=null; before creating a new request queue resolved the memory leak.
Many thanks again for finding this.
My test was quite dirty however, I think the release of memory should be done in the response and error handler functions to allow for interleaved requests. I'm not confident enough with android development, so maybe the android developer could add this and commit it to one of the upcoming releases?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I made a test and ensuring the queue.stop(); queue=null; before creating a new request queue resolved the memory leak.
Many thanks again for finding this.
My test was quite dirty however, I think the release of memory should be done in the response and error handler functions to allow for interleaved requests. I'm not confident enough with android development, so maybe the android developer could add this and commit it to one of the upcoming releases?