Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62798 - [glib2] Socket leak makes Next browser unstable
Attached to Project:
Arch Linux
Opened by Hugh Daschbach (hdasch) - Sunday, 02 June 2019, 19:29 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 02 June 2019, 21:15 GMT
Opened by Hugh Daschbach (hdasch) - Sunday, 02 June 2019, 19:29 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 02 June 2019, 21:15 GMT
|
DetailsDescription: Next browser unstable on Arch due to socket leak in glib2.
Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Sunday, 02 June 2019, 21:15 GMT
Reason for closing: Works for me
Additional comments about closing: Please update to glib 2.60.3.
Sunday, 02 June 2019, 21:15 GMT
Reason for closing: Works for me
Additional comments about closing: Please update to glib 2.60.3.
next-gtk-webkit.backtrace
Next browser use webkit2gtk (version 2.24.1-1 installed), which in turn, depends on glib2 (version 2.60.1-1 installed). The traceback for the Next browser crash is attached. But the traceback isn't as helpful as the observation that the process had 1024 sockets open at the time of the crash.
Chased this down to a socket leak in glib2. That leak has been fixed upstream: https://gitlab.gnome.org/GNOME/glib/commit/bdefe5f9e1eb739043ae19ac57fb00e905f482e2.
I've rebuild glib2 locally with that patch. It does seem to resolve the isuse.