|Summary:||[EFL][WK2] Crashes in websocket hybi test cases|
|Product:||WebKit||Reporter:||Chris Dumez <cdumez>|
|Component:||WebKit EFL||Assignee:||Chris Dumez <cdumez>|
|Severity:||Normal||CC:||laszlo.gombos, lucas.de.marchi, mcatanzaro|
|Version:||528+ (Nightly build)|
Description Chris Dumez 2013-03-11 05:01:05 PDT
Several websocket hybi test cases crash on WK2 EFL but not on WK1: http/tests/websocket/tests/hybi/broken-utf8.html http/tests/websocket/tests/hybi/close.html http/tests/websocket/tests/hybi/close-on-unload-and-force-gc.html http/tests/websocket/tests/hybi/extensions.html http/tests/websocket/tests/hybi/handshake-challenge-randomness.html http/tests/websocket/tests/hybi/multiple-subprotocols.html http/tests/websocket/tests/hybi/simple.html http/tests/websocket/tests/hybi/url-with-credential.html http/tests/websocket/tests/hybi/url-no-trailing-slash.html http/tests/websocket/tests/hybi/workers/multiple-subprotocols.html http/tests/websocket/tests/hybi/zero-length-text.html The backtrace is not really useful: crash log for WebProcess (pid <unknown>): STDOUT: Timed out waiting for initial response from web process STDERR: #PROCESS UNRESPONSIVE - WebProcess
Comment 1 Laszlo Gombos 2013-03-12 14:22:14 PDT
Is this a recent regression or has been like this for a while ?
Comment 2 Chris Dumez 2013-03-12 14:39:23 PDT
It's been like that for a while but we did not see it because the tests were skipped on EFL port.
Comment 3 Michael Catanzaro 2017-03-11 10:43:53 PST
Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.