We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Issue: Memory leak when disposing Verge App

Home Forums Bug Reports and Feature Requests Issue: Memory leak when disposing Verge App

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #55542

    Hi all!

    TLDR: Chromium based browsers appear to have a memory leak when disposing Verge apps. We are using a non-standard setup: see deployed example app and the code

    Our setup consists of a Next.js app that client-side renders the Verge app on a specific route, but also allows for toggling the Verge app on and off within the page as well – i.e. disposing the app, and reinitializing it. What I have found is that, on Chromium based browsers, calling dispose does not free the memory. It works as expected in Safari, and Firefox.

    Steps to reproduce:

    1. Navigate to the deployed example app in a Chromium based browser (Chrome, Chromium, and Brave were the ones I confirmed this behavior in)
    2. Note your current memory usage
    3. Click the “Verge Page” link to navigate to the page with the verge app
    4. Proceed to repeatedly do either/a combination of after the Verge app finishes loading:

      • Click the “Verge Enabled” checkbox to toggle the app off/on
      • Click the “Back” link, and then the “Verge Page” link to load the app again
    5. Check your memory usage again

    Of note, is that reloading the site at any point does free the memory.


    Hi, thanks for the report!

    We were able to reproduce this issue and we are currently investigating it.

    Co-founder and lead developer at Soft8Soft.


    This issue was fixed in the preview build of v.4.2. Please update and see if the problem is gone.

    Chief 3D Verger | LinkedIn | Twitter

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.