TheAssassin

I've had the VM running in the background, and just rediscovered it. It seems like it got stuck, perhaps due to your mem leak. I'm going to try to reproduce...

 Current state in my new VM. The last VM has been running fine for ~48 minutes, too, until I forgot about it. Let's see what happens.

 Another hour later, it uses around 250MiB more RAM. appimagelauncherd is running in the background, but we cannot be fully sure it's caused by the daemon. But it certainly...

I'll let that run for another while, then will try that out. Hopefully logging out and in works in a live ISO environment as expected.

I simply stopped appimagelauncherd now, and the memory leak seems to have stopped:   So, it seems appimagelauncherd is triggering the leak indeed. I have no idea how. But...

You can check the logs, it's not reintegrating if not necessary. I wonder why it would be writing every 30 seconds. As noted in #294 every 30 seconds it checks...

No, it looks like it's really monitoring your `$HOME`. IIRC we only monitor the first level, though, so that shouldn't be causing performance issues. If anything, you'd expect the daemon...

`update-desktop-database` is a workaround to make some distros/DEs just show the desktop entries within a reasonable amount of time. It must be run inside your home directory. What you describe...

Please fill in the missing information (most notably, AppImageLauncher version). Also, you need to post the URL of your AppImage.

> This issue should not have been dismissed instead of fixed Thanks @shoogle. If the issue would have been dismissed, it would be closed. I try my best to find...