[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
** Changed in: vscode Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/vscode/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
Set back to confirmed. While there have been changes to VSCode, that isn't "Firefox (Ubuntu)". The Ubuntu codebase for Firefox has not received any commits to fix this. The likely outcome of this issue is that we set Firefox (Ubuntu) to invalid because it is a bug in VSCode, not Firefox on Ubuntu. ** Changed in: firefox (Ubuntu) Status: Fix Committed => Confirmed ** Bug watch added: github.com/microsoft/vscode/issues #85344 https://github.com/microsoft/vscode/issues/85344 ** Also affects: firefox via https://github.com/microsoft/vscode/issues/85344 Importance: Unknown Status: Unknown ** No longer affects: firefox ** Also affects: vscode via https://github.com/microsoft/vscode/issues/85344 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/vscode/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
This PR seems to try to fix the bug : https://github.com/microsoft/vscode/pull/94503 It has been merged recently, so hopefully we might have this problem fixed in a future version of VSCode/VSCodium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
@sergiusens Fantastic findings! Thanks a lot for looking into this. This is also the underlying issue behind another issue I face when selfhosting VS Code: it simply crashes when opening a native Open dialog. Unsetting those env vars also fixes that issue! We got that bootstrapping code from Martin (@flexiondotorg): https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74 Including a tiny review from you: https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74#r32657237 I didn't really understand the original motive behind the `Gdk-pixbuf loaders` section. What do you think we can do here? What's the right way to move forward? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
If I were a betting person, I would put my stakes on gdk-pixbuf (https://github.com/snapcrafters/vscode/blob/master/files/bin/wrapper#L36) If that is part of code's environment, whatever it calls will leak that env into the callee... sergiusens@umbar:~$ snap run --shell code sergiusens@umbar:~$ cd $SNAP sergiusens@umbar:/snap/code/25$ cat electron-launch #!/usr/bin/env bash # On Fedora $SNAP is under /var and there is some magic to map it to /snap. # We need to handle that case and reset $SNAP SNAP=$(echo $SNAP | sed -e "s|/var/lib/snapd||g") if [ "$SNAP_ARCH" == "amd64" ]; then ARCH="x86_64-linux-gnu" elif [ "$SNAP_ARCH" == "armhf" ]; then ARCH="arm-linux-gnueabihf" elif [ "$SNAP_ARCH" == "arm64" ]; then ARCH="aarch64-linux-gnu" else ARCH="$SNAP_ARCH-linux-gnu" fi export XDG_CACHE_HOME=$SNAP_USER_COMMON/.cache if [[ -d $SNAP_USER_DATA/.cache && ! -e $XDG_CACHE_HOME ]]; then # the .cache directory used to be stored under $SNAP_USER_DATA, migrate it mv $SNAP_USER_DATA/.cache $SNAP_USER_COMMON/ fi mkdir -p $XDG_CACHE_HOME # Gdk-pixbuf loaders export GDK_PIXBUF_MODULE_FILE=$XDG_CACHE_HOME/gdk-pixbuf-loaders.cache export GDK_PIXBUF_MODULEDIR=$SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/2.10.0/loaders if [ -f $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders ]; then $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > $GDK_PIXBUF_MODULE_FILE fi # Create $XDG_RUNTIME_DIR if not exists (to be removed when https://pad.lv/1656340 is fixed) [ -n "$XDG_RUNTIME_DIR" ] && mkdir -p $XDG_RUNTIME_DIR -m 700 exec "$@" sergiusens@umbar:/snap/code/25$ if [ "$SNAP_ARCH" == "amd64" ]; then > ARCH="x86_64-linux-gnu" > elif [ "$SNAP_ARCH" == "armhf" ]; then > ARCH="arm-linux-gnueabihf" > elif [ "$SNAP_ARCH" == "arm64" ]; then > ARCH="aarch64-linux-gnu" > else > ARCH="$SNAP_ARCH-linux-gnu" > fi sergiusens@umbar:/snap/code/25$ sergiusens@umbar:/snap/code/25$ export XDG_CACHE_HOME=$SNAP_USER_COMMON/.cache sergiusens@umbar:/snap/code/25$ if [[ -d $SNAP_USER_DATA/.cache && ! -e $XDG_CACHE_HOME ]]; then > # the .cache directory used to be stored under $SNAP_USER_DATA, migrate it > mv $SNAP_USER_DATA/.cache $SNAP_USER_COMMON/ > fi sergiusens@umbar:/snap/code/25$ mkdir -p $XDG_CACHE_HOME sergiusens@umbar:/snap/code/25$ sergiusens@umbar:/snap/code/25$ # Gdk-pixbuf loaders sergiusens@umbar:/snap/code/25$ export GDK_PIXBUF_MODULE_FILE=$XDG_CACHE_HOME/gdk-pixbuf-loaders.cache sergiusens@umbar:/snap/code/25$ export GDK_PIXBUF_MODULEDIR=$SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/2.10.0/loaders sergiusens@umbar:/snap/code/25$ if [ -f $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders ]; then > $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > > $GDK_PIXBUF_MODULE_FILE > fi sergiusens@umbar:/snap/code/25$ firefox ExceptionHandler::GenerateDump cloned child 570327 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... sergiusens@umbar:/snap/code/25$ unset GDK_PIXBUF_MODULE_FILE sergiusens@umbar:/snap/code/25$ unset GDK_PIXBUF_MODULEDIR sergiusens@umbar:/snap/code/25$ firefox ###!!! [Child][MessageChannel] Error: (msgtype=0x370135,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv As you can see, env exported gets a crash, next, after unsetting, everything is fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
I can reliably reproduce this issue on a fresh install of Ubuntu 19.10. Default install of FF and deb install of VS code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
This happens for me on Ubuntu 19.10 only when vscode is installed as a snap. https://github.com/snapcrafters/vscode/issues/48 ** Bug watch added: github.com/snapcrafters/vscode/issues #48 https://github.com/snapcrafters/vscode/issues/48 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
