Mezzmo 5 w/ Samasung E Series TV gets Device Disconnected errors

[Lifferds]

Mezzmo and the Samsung are wired via LAN cable and I have gotten four Device Disconnected errors since updating yesterday. When That happens I am unable to stop the Media Server service through Mezzmo and must resort to the brute force Task Manager method or the even brutier reboot. Only then can I find Mezzmo listed as a source on the Samsung. Pain in the derriere.

I have also found that I can not push a video feed from PC (Win 10) to Samsung because, although the Samsung is listed in Media Devices, it does not show up in Play To. Actually, nothing shows up in Play To except Refresh which seems to do absolutely nothing.

Sigh, and I hate Netflix.

Tom

[Lifferds]

Mezzmo Server just crashed. Do you want the dump file?

[Paul]

Hi Tom,

Sorry for the problems. We have a patch that should help fix this problem. Email us at support [at] conceiva [dot] com.


Mezzmo Server just crashed. Do you want the dump file?

Yes, please :).

[Lifferds]

I'm afraid I'm going to have to resurrect this thread. Tonight I got a Device Disconnected error about every 15-20 minutes using Mezzmo 5.0.3.0.

I can go to the PC and, in Task Mgr, end the Mezzmo Server service. Mezzmo promptly restarts it and all is well for another 15-20 minutes. I can not stop the server in Mezzmo once the disconnect is received.
Will forward the dump files with this thread as subject.

Or maybe I won't as it is 25GB+, all tonight. <sigh>

Tom

Edit: I just tried it on a wireless connection to a Samsung C series with the same result.

Edit: When I try to stop the server through Mezzmo following a disconnect, I get an error 1053 response stating that it did not respond in a timely fashion, however, it appears as though the server did stop. After this, the log file blows up in size (3.45 GB for the first restart) with:
28554616 - May 28 15:12:08.486 [ThreadID:16c4] - [16C4] > ---------------------------------------------------------------------
28554617 - May 28 15:12:08.486 [ThreadID:16c4] - [16C4] INFO > 16C4 PostSelect: we are blocked on socket 5896
28554618 - May 28 15:12:08.486 [ThreadID:16c4] - [16C4] OUT > 16C4 PostSelect: (send) socket 5896, length = 61408, bytes not sent
28554619 - May 28 15:12:08.486 [ThreadID:16c4] - [16C4] > ---------------------------------------------------------------------
repeating over and over again.

[Paul]

Please email us at support [at] conceiva [dot] com and we'll provide a patch to try.