Bug 177935

Summary: [GTK] WebKitGTK hangs on http://www.flymeos.com/firmware.html when using a SOCKS ssh proxy
Product: WebKit Reporter: Cédric Bellegarde <cedric.bellegarde>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Major CC: bugs-noreply, chchkchk236, tibor.pacaj2
Priority: P2    
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Backtrace none

Cédric Bellegarde
Reported 2017-10-05 05:44:46 PDT
While visiting http://www.flymeos.com/firmware.html with Epiphany or Eolie (GNOME 3.26, WebKitGTK 2.18), WebKit hangs: - Current page is freezed - No more new pages are working
Attachments
Backtrace (72.88 KB, text/plain)
2018-02-27 05:52 PST, Cédric Bellegarde 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Cédric Bellegarde
Comment 1 2017-10-05 06:02:26 PDT
Title edited, seems to only happen while using a socks ssh proxy. Proxy is ok (working in firefox) while hang happens.
Cédric Bellegarde
Comment 2 2017-10-24 07:21:15 PDT
*** Bug 178725 has been marked as a duplicate of this bug. ***
Cédric Bellegarde
Comment 3 2018-02-26 04:31:37 PST
*** Bug 183120 has been marked as a duplicate of this bug. ***
Cédric Bellegarde
Comment 4 2018-02-26 04:45:24 PST
More details on this, seems WebKitGTK hangs while downloading with a socks proxy on: https://d3phbp7p78bdk9.cloudfront.net/83/foglio.js => no DNS resolution http://tongji-res1.meizu.com/resources/tongji/flow.js => 80 connection refused Do not seems related to libsoup (tested with libsoup directly, it reacts as supposed).
Cédric Bellegarde
Comment 5 2018-02-27 05:52:00 PST
Created attachment 334688 [details] Backtrace Managed to get this backtrace while WebKit was stuck on an URI.
Cédric Bellegarde
Comment 6 2018-02-27 07:31:01 PST
More information on this. Installed danted on my remote server and the issue is gone. So maybe OpenSSH does not respect SOCKS protocol and make WebKitGTK to hang. Feel free to close as it's a really particular use case.
Note You need to log in before you can comment on or make changes to this bug.