[Webkit-unassigned] [Bug 43902] New: flaky websocket/tests/frame-length-overflow.html

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=43902

           Summary: flaky websocket/tests/frame-length-overflow.html
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ukai at chromium.org
                CC: ap at webkit.org


chrome buildbot shows flaky failures of websocket/tests/frame-length-overflow.html
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=websocket%2Ftests%2Fframe-length-overflow.html

Actual test looks like:

Make sure WebSocket does not crash and report error when it sees length overflow

On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".

WebSocket is open
WebSocket received error frame
WebSocket received error frame
WebSocket is closed
PASS successfullyParsed is true

TEST COMPLETE


So, it received 2 error event before close.
I guess it would happen as follows:

 processBuffer post error event and leave buffer unchanged.
 before didClose is called, message loops runs again (more data comes from network or so) and calls processBuffer again (via didReceivedData or resumeTimerFired)
 it sees the same buffer again and post error event

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.