Bug 1515179

Summary: [abrt] glib-networking: JS_AbortIfWrongThread(): glib-pacrunner killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Maël Lavault <mael.lavault>
Component: glib-networkingAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: A.J.Caines+RedHat, gnome-sig, itblaked, jbastian, juan19932carlos, mcatanzaro+wrong-account-do-not-cc, mclasen, mikhail.zabaluev, raphael.kubo.da.costa, ribenakid, sardaukar.siet, sgallagh, tom, yurifun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c6e048623811a7c02d98363066656cd50570cb0f
Whiteboard: abrt_hash:bf0222557412331e87d24d422c541178c203c326;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-16 02:17:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Maël Lavault 2017-11-20 10:39:00 UTC
Version-Release number of selected component:
glib-networking-2.54.1-1.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=4412bf6ede71490d8fbc5d1d8188d207;i=508b5;b=33e61acea4f941fc86376b179ec8aa58;m=14391e7d8;t=55e67a4a40dad;x=726d43030e9a28aa
kernel:         4.13.12-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 JS_AbortIfWrongThread at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jsapi.cpp:5405
 #1 js::DestroyContext at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jscntxt.cpp:154
 #2 JS_DestroyContext at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jsapi.cpp:576
 #3 mozjs_pacrunner::~mozjs_pacrunner at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/modules/pacrunner_mozjs.cpp:158
 #5 libproxy::pacrunner_extension::get at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/extension_pacrunner.cpp:37
 #6 libproxy::proxy_factory::run_pac at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:419
 #7 libproxy::proxy_factory::get_proxies at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:216
 #8 px_proxy_factory_get_proxies at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:463
 #9 get_libproxy_proxies at glibproxyresolver.c:145
 #10 g_task_thread_pool_thread at gtask.c:1328

Potential duplicate: bug 1506044

Comment 1 Maël Lavault 2017-11-20 10:39:04 UTC
Created attachment 1355648 [details]
File: backtrace

Comment 2 Maël Lavault 2017-11-20 10:39:06 UTC
Created attachment 1355649 [details]
File: cgroup

Comment 3 Maël Lavault 2017-11-20 10:39:08 UTC
Created attachment 1355650 [details]
File: core_backtrace

Comment 4 Maël Lavault 2017-11-20 10:39:09 UTC
Created attachment 1355651 [details]
File: cpuinfo

Comment 5 Maël Lavault 2017-11-20 10:39:11 UTC
Created attachment 1355652 [details]
File: dso_list

Comment 6 Maël Lavault 2017-11-20 10:39:12 UTC
Created attachment 1355653 [details]
File: environ

Comment 7 Maël Lavault 2017-11-20 10:39:13 UTC
Created attachment 1355654 [details]
File: exploitable

Comment 8 Maël Lavault 2017-11-20 10:39:15 UTC
Created attachment 1355655 [details]
File: limits

Comment 9 Maël Lavault 2017-11-20 10:39:17 UTC
Created attachment 1355656 [details]
File: maps

Comment 10 Maël Lavault 2017-11-20 10:39:18 UTC
Created attachment 1355657 [details]
File: mountinfo

Comment 11 Maël Lavault 2017-11-20 10:39:20 UTC
Created attachment 1355658 [details]
File: open_fds

Comment 12 Maël Lavault 2017-11-20 10:39:21 UTC
Created attachment 1355659 [details]
File: proc_pid_status

Comment 13 Stephen Gallagher 2017-12-15 13:16:27 UTC
Similar problem has been detected:

I attempted to synchronize my GNOME Calendar. It appears to have crashed in libproxy. The crash does not appear if I disable my proxy configuration in GNOME settings.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=a23e45c356d2400e87124670148938f1;i=78aac;b=d1a3deec1a7441e08d0cdc7a5eb24b38;m=45f583429;t=560510a21ed01;x=f2475bc1a4374d51
kernel:         4.13.16-302.fc27.x86_64
package:        glib-networking-2.54.1-1.fc27
reason:         glib-pacrunner killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            13041

Comment 14 yurifun 2017-12-18 08:42:36 UTC
*** Bug 1526936 has been marked as a duplicate of this bug. ***

Comment 15 David Waring 2018-01-24 10:01:29 UTC
*** Bug 1538012 has been marked as a duplicate of this bug. ***

Comment 16 Bruno Antunes 2018-02-04 21:21:08 UTC
*** Bug 1541804 has been marked as a duplicate of this bug. ***

Comment 17 yurifun 2018-02-15 08:29:00 UTC
*** Bug 1545530 has been marked as a duplicate of this bug. ***

Comment 18 JuanC 2018-03-06 19:27:44 UTC
Similar problem has been detected:

I upgrade my OS two days ago and it problem appear. I usally use port to deploy web services right now Im using glassfish5, before the cras it was working 
well but now I cannot start the server running "asadmin start-domain" I get this error "There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server.
Command start-domain failed" but there is any aplication using that port. 
Also. I was seen and the network service is not running, it status is 

● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2018-03-06 14:03:41 EST; 1min 37s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1057 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
      CPU: 1.484s

Mar 06 14:03:41 Juancho systemd[1]: network.service: Control process exited, code=exited status=1
Mar 06 14:03:41 Juancho systemd[1]: Failed to start LSB: Bring up/down networking.
Mar 06 14:03:41 Juancho systemd[1]: network.service: Unit entered failed state.
Mar 06 14:03:41 Juancho systemd[1]: network.service: Failed with result 'exit-code'.

I have tried to use old linux core but the problem persist

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=ab025f867f3641cb8e64c6c6a42f9319;i=3018;b=1019b8e0fd0b412189e52b7b75518357;m=40265da4;t=566c0f17e7a27;x=218e29cb649e7856
kernel:         4.15.6-300.fc27.x86_64
package:        glib-networking-2.54.1-1.fc27
reason:         glib-pacrunner killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 yurifun 2018-03-15 12:06:13 UTC
Similar problem has been detected:

Lunch gnome-tweak-tool

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=7f5f62cf60e542f28f531d8704cae651;i=306373;b=8076ef5139774c6096788461089a4009;m=2b79ff9887;t=567724575cd68;x=d9be2572d6b20c9b
kernel:         4.15.7-300.fc27.x86_64
package:        glib-networking-2.54.1-1.fc27
reason:         glib-pacrunner killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 20 Michael Catanzaro 2018-04-16 02:17:47 UTC

*** This bug has been marked as a duplicate of bug 1538698 ***

Comment 21 Michael Catanzaro 2018-04-16 18:56:48 UTC

*** This bug has been marked as a duplicate of bug 1459779 ***

Comment 22 Andrew J. Caines 2018-07-06 14:58:15 UTC
*** Bug 1598827 has been marked as a duplicate of this bug. ***