Created attachment 1286028 [details]
File: backtrace

Created attachment 1286030 [details]
File: cgroup

Created attachment 1286032 [details]
File: core_backtrace

Created attachment 1286034 [details]
File: cpuinfo

Created attachment 1286036 [details]
File: dso_list

Created attachment 1286037 [details]
File: environ

Created attachment 1286039 [details]
File: exploitable

Created attachment 1286040 [details]
File: limits

Created attachment 1286041 [details]
File: maps

Created attachment 1286042 [details]
File: open_fds

Created attachment 1286043 [details]
File: proc_pid_status

Created attachment 1286044 [details]
File: var_log_messages

I get this one a lot. I'm specifying a proxy.pac file in network manager ui. It seems to make gnome shell crash from time to time.

*** Bug 1461954 has been marked as a duplicate of this bug. ***

This appears to be the same as bug 998232, which was fixed by "libproxy-0.4.11-crash.patch", but that got removed from the package at some point

Proposed as a Blocker for 26-final by Fedora user sgallagh using the blocker tracking app because:

 "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."

I see at least a dozen such crash notifications each day on my up-to-date F26 prerelease laptop.

But would you see it 'during installation or at first login after default install', or does it only happen after configuring a proxy? The criterion is only intended to cover crashes / AVCs that will appear on any install, or at least on a very large number of them.

(In reply to Adam Williamson from comment #17)
> But would you see it 'during installation or at first login after default
> install', or does it only happen after configuring a proxy? The criterion is
> only intended to cover crashes / AVCs that will appear on any install, or at
> least on a very large number of them.

Huh... I don't remember setting a proxy, but it seems that I did. So I guess you're right, this probably doesn't fit that blocker criterion.

-1 Blocker.

And given that we're in Final Freeze and I don't want to destabilize anything, I'll say -1 FE as well; it can be fixed in an update.

Discussed at 2017-06-29 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-06-29/f26-blocker-review.2017-06-29-16.00.html . As this only occurs when a proxy is configured, it doesn't really violate the criteria, so this is rejected as a blocker. We also decided not to grant a freeze exception as the issue can quite well be fixed by an update.

I have gotten this a few times today, the day after upgrading to F26.  GNOME (and all open GUI apps) crash and I am left at a login screen.

I am using a proxy.pac file configured in network manager.

Not sure if there is a relationship here:  I also have websocket connection issues with Epiphany when using the proxy.pac file which has prevented me from using Epiphany as my preferred browser.

I do not experience these proxy-related issues when using Firefox with the same proxy.pac file (specified in FF's preferences configuration).

libproxy-0.4.15-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa537fe626

libproxy-0.4.15-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-04bf7c03b8

libproxy-0.4.15-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-04bf7c03b8

libproxy-0.4.15-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa537fe626

I'm still seeing the crash with libproxy-0.4.15-2.

(In reply to Mark Salter from comment #25)
> I'm still seeing the crash with libproxy-0.4.15-2.

Can you post a backtrace of the crash, and confirm that you have restarted your system and that the updated version of libproxy is definitely being used?

Installed libproxy-0.4.15-2.fc26, restarted the laptop, still seeing crashes in glib-pacrunner:

Process 5419 (glib-pacrunner) of user 1000 dumped core.
                                                                
Stack trace of thread 5424:
#0  0x00007fa8ac2d9240 _Z21JS_AbortIfWrongThreadP9JSRuntime (libmozjs-38.so)
#1  0x00007fa8ac2dc412 _ZN2js14DestroyContextEP9JSContextNS_18DestroyContextModeE (libmozjs-38.so)
#2  0x00007fa8ac514cdf _ZN15mozjs_pacrunnerD0Ev (pacrunner_mozjs.so)
#3  0x00007fa8aef52848 _ZN8libproxy19pacrunner_extension3getENSt7__cxx1112basic_stringIcSt11char_traitsIcES
#4  0x00007fa8aef56f1a _ZN8libproxy13proxy_factory7run_pacERNS_3urlERKS1_RSt6vectorINSt7__cxx1112basic_stri
#5  0x00007fa8aef57da2 _ZN8libproxy13proxy_factory11get_proxiesENSt7__cxx1112basic_stringIcSt11char_traitsI
#6  0x00007fa8aef581f2 px_proxy_factory_get_proxies (libproxy.so.1)
#7  0x000055b9fb93f9fd get_libproxy_proxies (glib-pacrunner)
#8  0x00007fa8af758086 g_task_thread_pool_thread (libgio-2.0.so.0)
#9  0x00007fa8af1daf00 g_thread_pool_thread_proxy (libglib-2.0.so.0)
#10 0x00007fa8af1da536 g_thread_proxy (libglib-2.0.so.0)
#11 0x00007fa8ae0df36d start_thread (libpthread.so.0)
#12 0x00007fa8aec8ab8f __clone (libc.so.6)

libproxy-0.4.15-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

As said above, this is still happening for me with libproxy-0.4.15-2.fc26.

It works fine with libproxy-webkitgk4 instead of libproxy-mozjs, so it seems that spidermonkey is much more picky about being used from multiple threads in recent versions. The spidermonkey support was changed pretty significantly in libproxy 0.4.15 to use mosjs38, although the changes seem pretty reasonable:

https://github.com/libproxy/libproxy/commit/d5a6425d2ebfb62701b99427dcd511ebdf3181c7

I don't think it's "in recent versions"; spidermonkey has always been picky about that.

FWIW note that the pacrunner caching code in extension_pacrunner.cpp never actually worked anyway; nothing ever sets this->last, so the "if (this->last == pac)" check *always* fails, so every pacrunner will just get created and used once and then deleted (and replaced by an identical copy of itself) on the next call. That's why in the old version of the crash-fix patch I just got rid of it altogether.

I just updated Fedora:

libproxy.x86_64                        0.4.15-2.fc26               @updates     
libproxy-mozjs.x86_64                  0.4.15-2.fc26               @updates     

I'm still getting the error.

Running latest fedore26, I am also seeing the same errors when a system proxy is defined.

It causes problems for gnome-software (pops up several warnings about being unable to reach various addresses), and trying to build things with flatpak (can't get remote sources).

libproxy-0.4.15-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

This also seems to be the source for at least one instance of abrtd getting stuck at 100% cpu for me ( bug 1416310 ).

As it is now, setting a system proxy renders all my (F26) systems very unstable.

(In reply to Nikolai Vincent Vaags from comment #35)
> This also seems to be the source for at least one instance of abrtd getting
> stuck at 100% cpu for me ( bug 1416310 ).
> 
> As it is now, setting a system proxy renders all my (F26) systems very
> unstable.

I can confirm this. I had no issues until I configured a proxy in nmcli. A few moments late I had an exception (https://bugzilla.redhat.com/show_bug.cgi?id=1474972). Unfortunately it looks like the dump contains several aspects of my account IDs so the BZ is private.

*** Bug 1476306 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I have the following automatic proxy configuration script set: http://pac.pucrs.br/portoalegre.pac

This script is provided by my unversity to allow acess to restricted cientific portals away from campus, it work as expected on chrome, firefox and other OSes, but causes glib-pacrun to constantelly silently crash in the background floading my /var with coredumps

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=6ca830dd310048ada632c115489d96a2;i=1aa11;b=9219bd408a804b939183410b616ac49e;m=413811c;t=55814e710c6a1;x=4bfff45d16bbc5e5
kernel:         4.12.8-300.fc26.x86_64
package:        glib-networking-2.50.0-2.fc26
reason:         glib-pacrunner killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Created attachment 1320761 [details]
File: backtrace

Similar problem has been detected:

Running OpenShot Video Editor - keeps crashing

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=10b9a30d4fb54fd895522fe89f53609e;i=170ee;b=24046b571c9141f39dfc48235cc9386f;m=893f1099d;t=558417bbfad18;x=4a49d49052800b46
kernel:         4.12.9-300.fc26.x86_64
package:        glib-networking-2.50.0-2.fc26
reason:         glib-pacrunner killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Logged in after a system update/reboot. Using network proxy settings

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: JS_AbortIfWrongThread
executable:     /usr/libexec/glib-pacrunner
journald_cursor: s=db9a0ae050b445c091ca725da939354b;i=4fb0b;b=36478035a4544ed8b67c0e7e48abca33;m=2c3c5dc;t=5593aea23a921;x=49ff5f1a81378564
kernel:         4.12.12-300.fc26.x86_64
package:        glib-networking-2.50.0-2.fc26
reason:         glib-pacrunner killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1601400001

Fedora 27 has the same issue:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/glib-pacrunner'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f61c2e7e510 in JS_AbortIfWrongThread(JSRuntime*) ()
   from /lib64/libmozjs-38.so
[Current thread is 1 (Thread 0x7f61be8d8700 (LWP 5262))]
Missing separate debuginfos, use: dnf debuginfo-install glib-networking-2.54.1-1.fc27.x86_64
(gdb) bt
#0  0x00007f61c2e7e510 in JS_AbortIfWrongThread(JSRuntime*) ()
    at /lib64/libmozjs-38.so
#1  0x00007f61c2e8f512 in js::DestroyContext(JSContext*, js::DestroyContextMode) () at /lib64/libmozjs-38.so
#2  0x00007f61c30b9e4f in mozjs_pacrunner::~mozjs_pacrunner() ()
    at /usr/lib64/libproxy/0.4.15/modules/pacrunner_mozjs.so
#3  0x00007f61c5e12ca8 in libproxy::pacrunner_extension::get(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, libproxy::url const&) () at /lib64/libproxy.so.1
#4  0x00007f61c5e1737a in libproxy::proxy_factory::run_pac(libproxy::url&, libproxy::url const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) () at /lib64/libproxy.so.1
#5  0x00007f61c5e18202 in libproxy::proxy_factory::get_proxies(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) ()
    at /lib64/libproxy.so.1
#6  0x00007f61c5e18652 in px_proxy_factory_get_proxies ()
    at /lib64/libproxy.so.1
#7  0x000056301a1a2bad in get_libproxy_proxies ()
#8  0x00007f61c661bdf6 in g_task_thread_pool_thread ()
    at /lib64/libgio-2.0.so.0
#9  0x00007f61c609be90 in g_thread_pool_thread_proxy ()
    at /lib64/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#10 0x00007f61c609b4c6 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#11 0x00007f61c4f8c5e9 in start_thread () at /lib64/libpthread.so.0
#12 0x00007f61c5b40e2f in clone () at /lib64/libc.so.6
(gdb)

I was told that libproxy may not be thread-safe.  Here is a workaround
in Qt to run libproxy functions in one thread only:

https://codereview.qt-project.org/#/c/200463/

I can add that I observe this bug on F27 as well. My Fedora was upgraded on this machine since F24. I'm running libproxy-0.4.15-4.fc27.x86_64.

Possible duplicate: bug #1515179

*** Bug 1538698 has been marked as a duplicate of this bug. ***

*** Bug 1540676 has been marked as a duplicate of this bug. ***

*** Bug 1515179 has been marked as a duplicate of this bug. ***

*** Bug 1507894 has been marked as a duplicate of this bug. ***

*** Bug 1506254 has been marked as a duplicate of this bug. ***

*** Bug 1541651 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

I still have this bug on Fedora 28. I encountered it 78 times according to abrt since I upgraded yesterday....

I'll just reiterate from comment 15 that I believe this would be fixed by bringing back libproxy-0.4.11-crash.patch

libproxy-0.4.15-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ca19d423ce

libproxy-0.4.15-6.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ca19d423ce

libproxy-0.4.15-6.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Please release this fix for Fedora 27 as well.