Cast a m3u8 streaming will throw "Fatal Error: code = 1" when cast certain .ts segment

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Cast a m3u8 streaming to chromecast by my developing android app
2. m3u8 file and .ts extension segment files are at my local server (Not CORS 
problem)
3. It will start to cast streaming smoothly, but sometimes It will throw error 
message randomly when cast certain .ts extension file. 

What is the expected output? What do you see instead?
Uncaught TypeError: Converting circular structure to JSON
window.mediaManager.onError
X.Ka
g.Ka
wb
tb
(anonymous function)
...
...
...
Fatal Error: code = 1

more message is as attached

What version of the product are you using? On what operating system?
Streaming server : Mac os 10.10.2
Custom Receiver : (cast-custom-receiver) 
https://github.com/googlecast/cast-custom-receiver
cast_receiver.js : 2.0.0 version
media_player.js: 1.0.0 version

Please provide any additional information below.

Original issue reported on code.google.com by newfun....@gmail.com on 16 Mar 2015 at 9:42

Attachments:

• 1.png
• 2.png

[GoogleCodeExporter]

Original comment by newfun....@gmail.com on 16 Mar 2015 at 9:46

Attachments:

• 3.png

[GoogleCodeExporter]

Can you provide a sample stream for us to test?

Original comment by jonathan...@google.com on 18 Mar 2015 at 1:16

• Changed state: NeedInfo

[GoogleCodeExporter]

Below is the sample link:
https://drive.google.com/file/d/0ByoZJAoAfH7MX1F4b2hRa3cyM28/view?usp=sharing

You can access playlist.m3u8 to start streaming.  Thanks.

2015-03-18 9:16 GMT+08:00 <google-cast-sdk@googlecode.com>:

Original comment by newfun....@gmail.com on 18 Mar 2015 at 2:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For this sample case, it always throws error like pictures as attached when 
deal with 1426645644segment_v00009.ts.

Original comment by newfun....@gmail.com on 18 Mar 2015 at 4:15

[GoogleCodeExporter]

Any news here?
I have the same issue!

Original comment by b95505017 on 23 Mar 2015 at 4:56

[GoogleCodeExporter]

We are looking into the issue.

Original comment by jonathan...@google.com on 23 Mar 2015 at 9:54

• Changed state: Acknowledged