After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 571527 - gvfsd-http crashed with SIGSEGV in g_hash_table_lookup()
gvfsd-http crashed with SIGSEGV in g_hash_table_lookup()
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: http backend
1.1.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
: 572143 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-12 19:31 UTC by Pedro Villavicencio
Modified: 2009-03-10 14:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Pedro Villavicencio 2009-02-12 19:31:13 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/328413

"I don't know what gvfsd-http was doing at the moment, it just crashed. I was listening to audio in Totem"

".

+ Trace 212520

Thread 3 (process 4744)

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_102
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 px_proxy_factory_get_proxies
    from /usr/lib/libproxy.so.0
  • #4 get_proxy_sync
    at soup-proxy-resolver-libproxy.c line 174
  • #5 resolve_thread
    at soup-proxy-resolver-libproxy.c line 122
  • #6 g_thread_create_proxy
    at /build/buildd/glib2.0-2.19.6/glib/gthread.c line 635
  • #7 start_thread
    from /lib/libpthread.so.0
  • #8 clone
    from /lib/libc.so.6
  • #9 ??

Thread 1 (process 4720)

  • #0 IA__g_hash_table_lookup
    at /build/buildd/glib2.0-2.19.6/glib/ghash.c line 195
  • #1 CORBA_ORB_resolve_initial_references
    at corba-orb.c line 810
  • #2 gconf_get_config_listener
    at gconf.c line 2534
  • #3 gconf_get_config_server
    at gconf.c line 2242
  • #4 gconf_engine_connect
    at gconf.c line 364
  • #5 gconf_engine_get_default
    at gconf.c line 575
  • #6 gconf_client_get_default
    at gconf-client.c line 432
  • #7 gconf_config_cb
    from /usr/lib/libproxy/0.2.3/plugins/gnome.so
  • #8 px_proxy_factory_get_proxies
    from /usr/lib/libproxy.so.0
  • #9 get_proxy_sync
    at soup-proxy-resolver-libproxy.c line 174
  • #10 resolve_thread
    at soup-proxy-resolver-libproxy.c line 122
  • #11 g_thread_create_proxy
    at /build/buildd/glib2.0-2.19.6/glib/gthread.c line 635
  • #12 start_thread
    from /lib/libpthread.so.0
  • #13 clone
    from /lib/libc.so.6
  • #14 ?? 






Comment 1


Alexander Larsson





          2009-03-02 12:32:22 UTC
        



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






Comment 2


Dan Winship





          2009-03-02 15:47:28 UTC
        



This is basically libsoup's fault by way of libproxy. Should have a fix for tonight's release.







Comment 3


Sebastien Bacher





          2009-03-10 09:09:06 UTC
        



Dan, did you fix it in 2.25.92?






Comment 4


Dan Winship





          2009-03-10 14:16:14 UTC
        



I ended up missing the 2.25.92 deadline.

This is fixed in trunk by virtue of deprecating the libproxy backend in favor of using gconf directly again. For 2.26.1 I plan to make it use libproxy again; either there'll be a libproxy release before then fixing the bugs, or else libsoup will be a little bit more clever and only call libproxy in the cases that won't trigger the bugs.