deja-dup 38.0 was released with the ulimit workaround removed for
compatibility with the latest webkit release.

** Changed in: deja-dup
       Status: New => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.

  [regression] deja-dup-monitor crashed with SIGSEGV in

Status in Déjà Dup:
  Fix Released
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
Status in deja-dup source package in Xenial:
Status in deja-dup source package in Artful:
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 1000000" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
   PATH=(custom, no user)
   Segfault happened at: 0x7ff1c3dda588:        movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
   ?? () from /usr/lib/x86_64-linux-gnu/
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
std::lock_guard<bmalloc::StaticMutex>&) () from 
   bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap> >::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to