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 421890 - rhythmbox crashed with SIGSEGV in gnome_vfs_context_get_cancellation()
rhythmbox crashed with SIGSEGV in gnome_vfs_context_get_cancellation()
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Other
2.19.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
gnome[unmaintained]
: 495901 550878 552059 566418 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-23 14:09 UTC by Sebastien Bacher
Modified: 2018-08-17 13:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sebastien Bacher 2007-03-23 14:09:17 UTC 
The bug has been opened on https://launchpad.net/bugs/94893

"Binary package hint: rhythmbox

suddendly it crashed.
i was running firefox, zend and gaim.
wasn't doing nothing special (something which require a lot of microprocessor and/or ram to work) at the moment.

ProblemType: Crash
Architecture: i386
Date: Thu Mar 22 17:03:08 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/rhythmbox
...
.

+ Trace 121450

Thread 1 (process 11259)

  • #0 _gnome_vfs_handle_do_read
    at gnome-vfs-handle.c line 132
  • #1 gnome_vfs_read_cancellable
    at gnome-vfs-cancellable-ops.c line 135
  • #2 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1232
  • #3 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #4 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #5 g_thread_create_proxy
    at gthread.c line 591
  • #6 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #7 clone
    from /lib/tls/i686/cmov/libc.so.6" 






Comment 1


bboissin+gnomebug





          2007-08-24 20:03:37 UTC
        



I could reproduce this bug (just create a buggy network environment with iptables) while having rhythmbox trying to download cover arts.

The thing I noticed is that handle->uri was buggy (small address)

see below:




+
Trace
    157685






Thread NaN
          (LWP 18880)


    

  • 
#0
_gnome_vfs_handle_do_read

    
                at gnome-vfs-handle.c
                  line
                  132

    

    • 

  • 
#1
gnome_vfs_read_cancellable

    
                at gnome-vfs-cancellable-ops.c
                  line
                  135

    

    • 

  • 
#2
_gnome_vfs_job_execute

    
                at gnome-vfs-job.c
                  line
                  1232

    

    • 

  • 
#3
thread_entry_point

    
                at gnome-vfs-job-queue.c
                  line
                  65

    

    • 

  • 
#4
??

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#5
??

    • 

  • 
#6
??

    • 







$1 = (GnomeVFSHandle *) 0xb73ca3e8
(gdb) print handle->uri
$2 = (GnomeVFSURI *) 0x571e4
(gdb) print *handle->uri
Cannot access memory at address 0x571e4







Comment 2


Sebastien Bacher





          2007-08-28 14:49:02 UTC
        



comment on the ubuntu bug

"

Steps for reproducing:

# add entries for xml.amazon.com
sudo iptables -A INPUT -p tcp --src 207.171.166.90 -m limit --limit 5/second -j DROP
sudo iptables -A INPUT -p tcp --src 72.21.211.37 -m limit --limit 5/second -j DROP
sudo iptables -A INPUT -p tcp --src 72.21.207.8 -m limit --limit 5/second -j DROP

then play files which you don't already have the cover art (additionaly I make the network up/down :)

for me it produced the crash quite easily:




+
Trace
    158545






Thread NaN
          (LWP 18880)


    

  • 
#0
_gnome_vfs_handle_do_read

    
                at gnome-vfs-handle.c
                  line
                  132

    

    • 

  • 
#1
gnome_vfs_read_cancellable

    
                at gnome-vfs-cancellable-ops.c
                  line
                  135

    

    • 

  • 
#2
_gnome_vfs_job_execute

    
                at gnome-vfs-job.c
                  line
                  1232

    

    • 

  • 
#3
thread_entry_point

    
                at gnome-vfs-job-queue.c
                  line
                  65

    

    • 

  • 
#4
??

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#5
??

    • 

  • 
#6
??

    • 







$1 = (GnomeVFSHandle *) 0xb73ca3e8
(gdb) print handle->uri
$2 = (GnomeVFSURI *) 0x571e4
(gdb) print *handle->uri

obviously the uri is wrong (the adress is way too small), I think it was somehow changed by something, it could be:
gnomevfs python binding not doing a incref, or gnomevfs."






Comment 3


eduardgrebe





          2007-11-16 13:25:54 UTC
        



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






Comment 4


Cosimo Cecchi





          2008-09-04 17:47:38 UTC
        



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






Comment 5


Cosimo Cecchi





          2008-09-13 09:44:24 UTC
        



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






Comment 6


palfrey





          2009-01-03 20:31:51 UTC
        



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






Comment 7


André Klapper





          2018-08-17 13:48:26 UTC
        



gnome-vfs got deprecated in 2008.

gnome-vfs is not under active development anymore and had its last code changes
in 2011. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gnome-vfs/commits/master

gio (in glib) and gvfs are its successors. See https://developer.gnome.org/gio/stable/ch33.html and https://people.gnome.org/~gicmo/gio-migration-guide/ for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of glib/gio/gvfs. Thanks!