Duplicati keeps taking more and more memory even when idle.
version 2.0.8.1 on mac os 13.6.1
Right now its using 4.5GB. It started at 5MB used
The file set is local, ~300MB, 421 files
Do you mean it increases while idle, or it remains high when idle?
Is there a backup or other work ever done? To what storage type?
Is Remote volume size on Options screen still at 50 MB default?
is similar to this, and you can look over the questions from there too.
This might also be a mono problem. If so, mono’s going away soon…
The current testing versions of Duplicati are replacing it with .NET 8.
What’s your mono --version number? Note mono’s pretty stagnant.
I noticed the memory footprint peaked at 24GB.
Note: this is for Duplicati.app (macOS), mono-sgen memory consumption stayed below 250MB.
remote size is 50 MB. again the backup set is only ~ 300MB and I have no other duplicati jobs setup on this machine
I don’t know what the difference is between duplicati.app and mono-sgen so excuse my limited knowledge.
It hasn’t happened since a restart so I will have to monitor for if/when it happens again.
How do I check mono version?
OK, so maybe backups were being run, and detailed memory behavior is not well known.
What storage type is the backup destination?
What your tool may say is Duplicati is part of mono. It’s two processes. Both do something.
The split doesn’t seem to be documented, but Garbage collector talks about memory care.
If your tool has a PID number, you can try opening a Terminal to view different names, e.g.
# ps -p 90149
PID TTY TIME CMD
90149 pts/2 00:00:22 mono
# ps -p 90149 -F
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
me 90149 24325 2 39506 44340 0 09:16 pts/2 00:00:22 Duplicati /usr/lib/duplicati/Duplicati.GUI.TrayIcon.exe
This is just background. All of mono is running Duplicati, so something’s not working right.
Knowing what storage type you use (and maybe testing with another) may cut that down.
typed into a terminal.
sorry for the delay, i forgot about this.
here is the output
Mono JIT compiler version 6.12.0.199 (2020-02/f648ec1e0a6 Wed Jun 14 09:24:35 EDT 2023)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:
SIGSEGV: altstack
Notification: kqueue
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: hybrid
GC: sgen (concurrent by default)
the memory consumption is very high given that the backup set is ~ 300MB
if I quit the .app in Activity Monitor, the memory is released and duplicati continues to be accessible through the web interface. I can’t find any way to autostart without using the troublesome .app
6.12.0.199 sounds like almost the latest (not that latest is perfect, as mono project is not active).
Mono 6.12.0.200 Release Notes doesn’t mention anything sounding like it should help situation.
What storage type is the backup destination? Have you run anything else to see what happens?
For Mac, you probably need to hear from someone with one. Can you tell if Duplicati restarted? What user is Duplicati? When does it normally start? At boot? Login? See About → System info UserName and StartedBy for some clues on what you have. What do you mean by “autostart”?
We can also check your configuration to make sure it looks reasonable. You could post it using
Export As Command-line and redact personal information. Even source paths aren’t so relevant.
Possibly something will show up, but possibly this is a mono issue and needs the 2.0.9.x release which isn’t quite ready for general use. Some versions seem fine for testing, but quality may vary.