Closed Bug 1472589 Opened Last year Closed 9 months ago
Snap sandbox breaks parent process crash reporting
47 bytes, text/x-phabricator-request
|Details | Review|
I have a patch for bug 1461848 that fixes crash reporting for child processes, but not for the parent process; the dynamic linker can't find `libgtk-3.so.0` when launching the crash reporter GUI. My guess is that snapd starts tearing down the sandbox when the main process exits, but I haven't investigated.
I took a look, and problem might be a lot more boring than I thought: within the Snap container there is no GTK in /usr/lib or the other default paths; instead it's in /snap/firefox/N/usr/lib (where N is the package revision) and this is communicated via $LD_LIBRARY_PATH. But we unset $LD_LIBRARY_PATH when launching the crash reporter, for reasons explained in bug 407229 and the comment at . It looks like we dynamically load libcurl, so maybe we could do the unsetenv after the exec (in the crashreporter executable itself) instead of before?  https://searchfox.org/mozilla-central/rev/007b66c1f5f7a1b9a900a2038652a16a020f010c/toolkit/crashreporter/nsExceptionHandler.cpp#831
Component: Release Automation: Snap → Crash Reporting
Product: Release Engineering → Toolkit
QA Contact: jlorenzo
See Also: → 407229
Assignee: nobody → jld
Priority: -- → P1
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/dbf72abf5597 Fix parent process crash reporting in the Snap package environment. r=ted,jlorenzo
Attachment #9041341 - Flags: approval-mozilla-beta?
You need to log in before you can comment on or make changes to this bug.