Avatar for user155558


Member since May 2023 • Last active May 2023
  • 1 conversations

Most recent activity

  • in Bangle.js
    Avatar for user155558

    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?

  • in Bangle.js
    Avatar for user155558

    Hello Gordon, hello rigrig,

    many thanks for replying to this so quickly, it's very nice from you. In fact, I also have only very limited time these days, but I want to try what you suggested as soon as I can.

  • in Bangle.js
    Avatar for user155558


    I am calling regularly Bangle.http("https://...") from my Bangle.js 2. For testing, I do it at a rate of 1 request/sec, while ensuring not starting a new request before the previous one returns.

    After establishing the Bluetooth connection to gadgetbridge, it works fine for some time, but after some minutes, issues occur. These are:

    • random bluetooth disconnects
    • unresponsive hanging of Gadgetbridge
    • bluetooth reconnect feature not working reliably

    I have enabled USB-Debugging and tried to track the memory usage of gadgetbridge:

    watch -n1 adb shell dumpsys meminfo com.espruino.gadgetbridge.banglejs

    and I see that the "TOTAL" memory is increasing constantly at a rate of about 1MB/s.

    Is it possible that there is a memory leak in Bangle.js gadgetbridge and has somebody else seen this behaviour already? How can I track this down further?

    I would appreciate greatly any help.

    Many thanks!