This is a likely a serving issue, the server is replying with two different content lengths.

ERR_CONTENT_LENGTH_MISMATCH is an error generated by the HTTP loading code.
(Generally when the number of bytes returned doesn't match the content-length)
The case for when it is triggered is somewhat complicated, but generally looks right.

We would need an example URL to determine if this a problem with the serving code or something chrome is doing wrong.

M54 is not a realistic milestone hence tagging for M56.

Generally this indicates a problem with the server delivering the content.

(May work on other browsers because they aren't as strict in verifying content lengths).

If you have a specific URL to reproduce on please include it.

The content length recieved in the response header is same as the length of the audio.
I am sorry I wont be able to give the example url but I believe this issue has occured to quite a few people.
https://bugs.chromium.org/p/chromium/issues/detail?id=158245

https://bugs.chromium.org/p/chromium/issues/detail?id=109751

The other bug reports seem to be different problems.
I did some experimentation to see if I could reproduce this bug, but I could not.

In liu of a url that reproduce the problem, could you bring up dev console (F12) and attach the contents of the network tab to this bug?

Also, chrome://net-internals has a lot of useful information that you could
attach.

Unable to reproduce the issue on win10 chrome version 57.0.2929.0 and dev 56.0.2924.3 - Played few sample Mp3 audio files

taherlakdawala9@, Could you please respond as per comment #6

You can try playing an audio file of around 30 mins by fetching directly from Server location.

Below you can find some information from chrome://net-internals

    HTTP_TRANSACTION_READ_RESPONSE_HEADERS
                         --> HTTP/1.1 200 OK
                             X-Powered-By: Servlet/3.0
                             Date: Fri, 25 Nov 2016 08:59:41 GMT
                             Content-Type: audio/mpeg
                             Last-Modified: Tue, 08 Nov 2016 09:49:56 GMT
                             Content-Length: 29500692
                             Content-Language: en-US
                             Set-Cookie: [166 bytes were stripped]
                             Set-Cookie: [77 bytes were stripped]
t=401784 [st=325]     -HTTP_TRANSACTION_READ_HEADERS
t=401784 [st=325]      HTTP_CACHE_WRITE_INFO  [dt=0]
t=401784 [st=325]      HTTP_CACHE_WRITE_DATA  [dt=0]
t=401784 [st=325]      HTTP_CACHE_WRITE_INFO  [dt=1]
t=401785 [st=326]      URL_REQUEST_DELEGATE  [dt=0]
t=401785 [st=326]   -URL_REQUEST_START_JOB
t=401785 [st=326]    URL_REQUEST_DELEGATE  [dt=1]
t=401786 [st=327]    HTTP_TRANSACTION_READ_BODY  [dt=0]
t=401786 [st=327]    HTTP_CACHE_WRITE_DATA  [dt=0]
t=401786 [st=327]    URL_REQUEST_JOB_BYTES_READ
                     --> byte_count = 983
t=401786 [st=327]    HTTP_TRANSACTION_READ_BODY  [dt=0]
t=401786 [st=327]    HTTP_CACHE_WRITE_DATA  [dt=0]
t=401786 [st=327]    URL_REQUEST_JOB_BYTES_READ
                     --> byte_count = 7300
t=401787 [st=328]    HTTP_TRANSACTION_READ_BODY  [dt=0]
t=401787 [st=328]    HTTP_CACHE_WRITE_DATA  [dt=0]
t=401787 [st=328]    URL_REQUEST_JOB_BYTES_READ
                     --> byte_count = 1460
t=401787 [st=328]   +HTTP_TRANSACTION_READ_BODY  [dt=1]
t=401787 [st=328]      CANCELLED
t=401787 [st=328]      HTTP_CACHE_WRITE_INFO  [dt=1]
t=401788 [st=329] -REQUEST_ALIVE

Thank you for providing more feedback. Adding requester "eroman@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

 hubbe@, could you please take a look at comment #8

Unfortuntely #8 does not give any hints as to what is going wrong here. (It doesn't list show any error messages or odd behavior.) Logs from the "network" tab in the developer console might provide more information.

taherlakdawala9@ Please respond to comment#11 and provide the logs as requested.

taherlakdawala9@, Gentle Ping!

Closing this due to lack of followup.  This is almost certainly due to the server not sending us the right amount of data.  The request shown in comment #8 was canceled, rather than failing with ERR_CONTENT_LENGTH_MISMATCH, so was presumably for the wrong request.  We don't have enough data to follow up here, even in the unlikely case it is a Chrome issue.

Hi,

It seems that the audio works when it gets a 206 response code when fetched from different server.But the server i am using is sending a 200 Ok response and chrome doesnt download the whole audio from one request for a 200 Ok response.The chrome browser initiates another request with the same content length which breaks the connection.
Ideally Chrome should not initiate multiple requests to download the audio file.It should play the whole audio only with one request.
Can you please help me to configure chrome to play the whole audio through one request.