Consumes too much RAM (5GB for 200+ nodes)

[shibaFoss]

I haven't used this app for a long time, but the new version (installed via flatpak) may have a memory leak issue. Here's a screenshot of it using nearly 5 GB of RAM. However, the file I was working on was not particularly large. It had around 200 nodes. image>https://imgur.com/a/JChxOkf

[phase1geo]

Out of curiosity, if you exit the application and restart it (reloading the same mindmap), how much memory is consumed?

[shibaFoss]

roughly around 40 mb https://imgur.com/a/9GV6BNk

[cknave]

This was happening to me. Opening a modestly sized file quickly consumed all available RAM. I got as far as tracing the allocations with massif (750 MB allocated by the XML parser, stack trace attached) before taking a closer look at my document.

The <images> section consisted of the same 4 lines repeated 500k times. A previous version must have had a bug writing this section.

I deleted all but the last group of images, and this fixed the problem.

This raises some questions:

• Are the XML parser results not being freed?
• Should this autosave function be debounced? The canvas is going to change frequently when scrolling, resizing the window, etc.

[phase1geo]

Looking at the source code, the loaded/saved XML doc pointers are being deleted. As for the issue of autosaving, the versions of Minder that are 16 and above (though I believe it started in one of the minor revs of 15), scrolling, panning, zooming and window resizing do not cause the .minder file to be saved. Only when items are added, changed, removed or moved within map cause saves to occur.

[phase1geo]

The issue with a ton of image data in the Minder file is alarming though. Does this still occur with the latest version of Minder?

[cknave]

So far it hasn't reoccurred