Resetting to Triaged, because the duplicates bug #1756817 and bug
#1756776 show the same characteristics as described in comment #50.
** Changed in: deja-dup (Ubuntu Bionic)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1751460
Title:
[regression] deja-dup-monitor crashed with SIGSEGV in
Gigacage::<lambda()>::operator()
Status in Déjà Dup:
New
Status in WebKit:
Fix Released
Status in deja-dup package in Ubuntu:
Triaged
Status in webkit2gtk package in Ubuntu:
Invalid
Status in deja-dup source package in Xenial:
Triaged
Status in deja-dup source package in Artful:
Triaged
Status in deja-dup source package in Bionic:
Triaged
Bug description:
Impact
------
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
----------
https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e
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
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
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
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
__pthread_once_slow (once_control=0x7ff1c404202c,
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
Gigacage::ensureGigacage() () from
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
bmalloc::Heap::Heap(bmalloc::HeapKind,
std::lock_guard<bmalloc::StaticMutex>&) () from
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap> >::getSlowCase() ()
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
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:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
