Anytype swallows ram

Describe the bug

Eats the ram. about 3 gb total. Even Anytype mobile hanged and **

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

    1. Go to ‘…’
    1. Click on ‘…’
    1. Scroll down to ‘…’
    1. See an error

Expected behavior

A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

  • OS: Android 10
  • Device: Samsung S8
  • Version: 0.0.49

Additional context

Add any other context about the problem here.froze** my phone and as well as computer

To Reproduce

Steps to reproduce the behavior:

    1. Open anytype
    1. Click on sets
    1. Create sets
    1. See an error. Computer hangs.

and same process on mobile too

Expected behavior

Not hanging.

Desktop (please complete the following information):

  • OS: ubuntu 20.04

  • Device: 4gb ram, i5 processor

  • Version: 0.18.57

  • OS: Android 11

  • Device: Realme 8 5g

  • Version: 0.2.3

Describe the bug

After deleting two sets (that is moving them to archive) Anytype RAM consumption went through the roof and the UI hanged out forever. After killing Anytype and it’s related process RAM consumption went from 15 out of 16 to 6 out of 16 and SWAP went from around 9 to 4.

To Reproduce

Steps to reproduce the behavior:

    1. Delete a set or two
    1. Wait for it.

Expected behavior

It does not hang out or eat ram.

Desktop (please complete the following information):

  • OS: Arch Linux x86_64 (Kernel 5.13.7-arch1-1)
  • Device: Dell XPS 13 9370
  • Version: 0.18.57
1 Like

You can kill the process (macOS, Linux) with pkill -ABRT anytypeHelper and send us the stacktrace (there will be active processes)

No issues for me. macOS 11.5.1 on Apple Silicon w/16GB RAM

@Vova No active process when freshboot. Will try after opening it.

@endac

@Vova

It takes almost 1.4 gb on fresh start me

@Vova How do i find stacktrace?

Is this what you meant? @Vova

You need to start the app from console

It’s important to send us data only if you see unusually high consumption of resources

Mac, Linux

Windows

It’s important to send us data only if you see unusually high consumption of resources

Oh boy, here we go:

Describe the bug

High RAM and CPU usage.

To Reproduce

Steps to reproduce the behavior:

    1. Navigate around
    1. Delete a set
    1. Restore a set
    1. Open some objects
    1. Delete a set
    1. Open the deleted set.

Expected behavior

It does not use so much RAM and CPU

Desktop (please complete the following information):

  • OS: Arch Linux x86_64 (Kernel 5.13.7-arch1-1)
  • Device: Dell XPS 13 9370
  • Version: 0.18.57

Additional context

I got a heap when it started going up, then started a profile and also gathered a goroutine, when the profile finished did another heap.

It is important to know that the attached files are from a fresh startup that already started in whitescreen and went nuts in resource consumption. The steps to reproduce is what I did the first time and it used so many resources (up to 6.9GB and 60% CPU) that when I went to gather the report files the logging software did not work, the connection was closed. So i guess my anytype is in bugged state for now on. I’ll erase the anytype folder to see if it corrects itself.

Files:report.zip

3 Likes

Hey, @lucasmmarino, @Srinath!

Could you check the behavior of Anytype in the latest version on the desktop?

In some cases there was a problem with opening Sets, but now it has been fixed.

1 Like

@Vova For me 0.18.58 solved the set opening issue on the first go. As I told Roman the only caveat is that these previously corrupted sets won’t sync anymore, but I’ll wait until the delete feature update and remove them, for now they seat in the archive.

Mobile 0.2.6 is also looking fine for the corrupted sets, they open just fine. It has other bugs but AFAIK they are already reported.

Thanks for the hard work!

1 Like

@Vova It works great now after the latest update.

1 Like