Comment 4 for bug 1572260

I don't know if I have the exact same problem, but in my case it is because gvfs-smb-browse tries to access a samba server (first problem is why does it try to contact it, I never browse samba shares) using ipv6
When gvfs-smb-browse uses the whole cpu core I can run a :
netstat -laputenW | grep gvfs
And see that gvfs is trying to contact an ipv6 address

I reproduced it at home (16.04) and at work (14.04, happens since a recent update, did not happen last month for example) :
- at home it tries to connect to the samba share of my internet box / router, using its public ipv6 address, so this will never ever work
- at work it tries to connect to some co workers windows 10 share, using local ipv6 addresses

I have solved my problem by :
- at home, using google ipv6 dns, that way gvfs can't get the ipv6 of my internet box and won't try to connect to it
- at work I just disabled ipv6 (switched to local link iirc)