Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

segfault in libcurl during install #2977

Closed
cmurf opened this issue Jun 24, 2019 · 10 comments
Closed

segfault in libcurl during install #2977

cmurf opened this issue Jun 24, 2019 · 10 comments

Comments

@cmurf
Copy link

cmurf commented Jun 24, 2019

Linux distribution and version

Fedora 30

Flatpak version

flatpak-1.4.1-1.fc30.x86_64
ostree-2019.2-1.fc30.x86_64
bubblewrap-0.3.3-2.fc30.x86_64
curl-7.64.0-7.fc30.x86_64

Description of the problem

Similar to issue 2934, except I'm seeing it during the installation of org.freedesktop.Platform. It doesn't always happen, maybe 50% of the time it happens. This is happening on a clean installation of Fedora 30.

Steps to reproduce

  1. No flatpak repos or anything else installed; /var/lib/flatpak/ is empty
  2. $ flatpak install --from com.slack.Slack.flatpakref

Contains gdb output for a coredump that was captured
https://bugzilla.redhat.com/show_bug.cgi?id=1723242
The dup that abrt found after multiple hours of dealing with debuginfos and gdb.
https://bugzilla.redhat.com/show_bug.cgi?id=1697566

@mwleeds
Copy link
Collaborator

mwleeds commented Jun 27, 2019

It's hard to see how this is a Flatpak bug. It's libcurl that's crashing.

@mwleeds mwleeds changed the title segfault at 1898 ip 00007f968c266764 sp 00007fff88462540 error 4 in libcurl.so.4.5.0 segfault in libcurl during install Jun 27, 2019
@cmurf
Copy link
Author

cmurf commented Jun 28, 2019

It's a bug because flatpak is failing to properly handle the libcurl crash in a way that lets me clearly know there's been a problem in a library flatpak depends on. From a user perspective, it looks like a flatpak crash.

@mwleeds
Copy link
Collaborator

mwleeds commented Jun 28, 2019

I don't know of any program which catches seg faults and converts them into another kind of error. I agree it seems like a Flatpak crash to the user, but maybe it's worth opening a bug report on libcurl in case they have some insight?

@cmurf
Copy link
Author

cmurf commented Jun 30, 2019 via email

@tansly
Copy link

tansly commented Jun 30, 2019

This is a libcurl bug, which is fixed. Fedora needs to update its libcurl to 7.65.

Actual crash happens at:
#0 multi_socket (multi=multi@entry=0x562b396fe710, checkall=checkall@entry=false, s=<optimized out>, ev_bitmask=2, running_handles=0x562b38e6bdb0) at ../../lib/multi.c:2652
See:
https://curl.haxx.se/mail/lib-2019-05/0031.html

Also see:
curl/curl#3904
curl/curl#3952

Commit fixing this: curl/curl@8581e19

Curl changelog says that it is fixed in 7.65.1 ( multi: track users of a socket better ). But Fedora 30 still has 7.64.

Better file a bug against Fedora.

@tansly
Copy link

tansly commented Jun 30, 2019

By the way, the same error also happens in gnome-software, again causing a segfault.

@cmurf
Copy link
Author

cmurf commented Jun 30, 2019

Fedora downstream bugs are:
flatpak
https://bugzilla.redhat.com/show_bug.cgi?id=1697566
gnome-sofware
https://bugzilla.redhat.com/show_bug.cgi?id=1723242

I changed both to curl.

The problem with the idea this is fixed in curl 7.65, is that version is already on Fedora Rawhide and I get the same crash there too, but far less often than on Fedora 30. It might be once in ~7GiB downloaded before I run into it. And it has only happened on large runtimes, so far only > 700MiB, nothing smaller.

@jay
Copy link

jay commented Jun 30, 2019

The problem with the idea this is fixed in curl 7.65, is that version is already on Fedora Rawhide and I get the same crash there too

The multi fixes are in 7.65.1. As was mentioned on the mailing list if you're still having problems please try master since it's possible there's already a fix in for it.

/cc @bagder

@cmurf
Copy link
Author

cmurf commented Jun 30, 2019

I mentioned in the libcurl-mailing list thread I'm using libcurl-7.65.1-1.fc31.x86_64

@mcatanzaro
Copy link
Collaborator

I agree that it's unlikely there's any flatpak bug here, certainly none actionable. (I would close this.)

I recommend reporting a new bug against libcurl, with a backtrace taken with libcurl-7.65.11-1.fc31. Having an updated backtrace might be important so that this isn't just a shot in the dark.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants