[Webkit-unassigned] [Bug 73404] New: [WebSocket] bufferedAmount calculation is wrong in CLOSING and CLOSED state

[bugzilla-daemon at webkit.org]

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

           Summary: [WebSocket] bufferedAmount calculation is wrong in
                    CLOSING and CLOSED state
           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: toyoshim at chromium.org
                CC: ap at webkit.org, abarth at webkit.org, tkent at chromium.org,
                    yutak at chromium.org


In WebSocket::close(), m_bufferedAmountAfterClose is set to m_channel->bufferedAmount() and state is changed to CLOSING.
On the other hand, WebSocket:bufferedAmount() returns m_channel->bufferedAmount() + m_bufferedAmountAfterClose in CLOSING state.
That means bufferedAmount is double counted in CLOSING state.
Also, in didClose(), we just added unhandledBufferedAmount to m_bufferedAmountAfterClose.
In CLOSE state, WebSocket::bufferedAmount() just returns m_bufferedAmountAfterClose. But still it contains previously added bufferedAmount() in addition to unhandledBufferedAmount.

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