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 671127 - No connect to server use ~98%CPU (sftp)
No connect to server use ~98%CPU (sftp)
Status: RESOLVED DUPLICATE of bug 724780
Product: gvfs
Classification: Core
Component: sftp backend
1.10.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2012-03-01 13:42 UTC by Cristian Aravena Romero
Modified: 2014-02-20 12:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
valgrind-nautilus.log (14.83 KB, application/x-xz)
2012-03-01 14:21 UTC, Cristian Aravena Romero
Details

Description Cristian Aravena Romero 2012-03-01 13:42:13 UTC
Open bug in launchpad.net
https://bugs.launchpad.net/bugs/943993

"I'm testing nautilus and file transfer and no connect to server and use 70%CPU. Attach backtrace"

  • #0 __GI___poll
    at ../sysdeps/unix/sysv/linux/poll.c line 87
  • #1 g_main_context_poll
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3402
  • #2 g_main_context_iterate
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3084
  • #3 g_main_loop_run
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3297
  • #4 daemon_main
    at daemon-main.c line 301
  • #5 main
    at daemon-main-generic.c line 39

Comment 1 Cristian Aravena Romero 2012-03-01 13:43:56 UTC
My tests are behind a firewall
Comment 2 Cristian Aravena Romero 2012-03-01 14:21:39 UTC
Created attachment 208784 [details]
valgrind-nautilus.log
Comment 3 Cristian Aravena Romero 2012-03-02 16:40:29 UTC
Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Seleccione otro visor e inténtelo de nuevo.
Comment 4 Cristian Aravena Romero 2012-03-02 17:14:35 UTC
I'm using proxy http.
Comment 5 Felix Möller 2012-07-29 10:15:07 UTC
Any chance this is related to bug #674348. Could you create a backtrace at when it uses the CPU?  Just attach with gdb -p <pid>.
Comment 6 Ondrej Holy 2014-02-20 12:50:51 UTC
It looks like it is same bug as Bug 724780. Marking as duplicate though this bug is older, however in the new bug there is more reproduction info...

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