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:
Delete a set or two
Wait for it.
Expected behavior
It does not hang out or eat ram.
Desktop (please complete the following information):
It’s important to send us data only if you see unusually high consumption of resources
Mac, Linux
Stop application if it’s running.
Can you please start Terminal. In Spotlight you can type “Terminal”
Ran the application through the terminal with this command (please correct the location of Anytype app if needed): ANYTYPE_LOG_LEVEL="*=DEBUG" ANYPROF=:6060 /Applications/Anytype.app/Contents/MacOS/Anytype
Use Anytype until you notice a higher consumption of resources
Use CTRL(CMD)-A and CTRL(CMD)-C to copy data from the browser and send it to the team or just send the automatically generated file
Windows
Stop application if it’s running.
Can you please start Terminal. In Search you can type “Terminal”
Ran the application through the terminal with this command (please correct the location of Anytype app if needed): set "ANYTYPE_LOG_LEVEL=*=DEBUG" && set "ANYPROF=:6060" && start C:\Users\Administrator\AppData\Local\Programs\anytype2\Anytype.exe
Use Anytype until you notice a higher consumption of resources
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.
@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.
