Sigh, I've never been able to reproduce this. Despite several people saying it's connected to Chrome Remote Desktop, we also have several reports of it happening without that involved.
I'm currently testing a workaround (committed to trunk) that sets a memory limit on the monitor process, as a quick and dirty hack to alleviate the effects of this bug. If anyone wants to test on their machine, you can edit /etc/xdg/autostart/deja-dup-monitor.desktop to change its Exec line to: Exec=bash -c "ulimit -v 1000000; /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor" X-GNOME-AutoRestart=true (change the x86_64-linux-gnu part as needed) I'd welcome reports of success or failure with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302416 Title: deja-dup monitor was taking 6GB of memory To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1302416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
