Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RealtimeStreaming Client crashes at the end of a connection (Invalid read size) #340

Open
danilogr opened this issue Jun 25, 2019 · 1 comment

Comments

@danilogr
Copy link
Contributor

This happened while I was testing on Unity 2018.4.2f1 on Windows 1903 with the RealtimeStreaming compiled as Debug. Server (HoloLens) crashed and caused the client (Unity) to crash.

I attached VisualStudio to Unity and this is what the library prints on the console:

DataBundleArgsImpl::~DataBundleArgsImpl()
RealtimeMediaSource::OnDataReceived(0)
Connection::RunSocketLoop - Tid: 20584 
Connection::OnHeaderReceived() - Tid: 20584 
Connection::OnHeaderReceived() - Invalid read size 
Exception thrown at 0x00007FF88D8AA839 (KernelBase.dll) in Unity.exe: WinRT originate error - 0x800704B1 : 'The device is not currently connected but it is a remembered connection.'.
Exception thrown at 0x00007FF88D8AA839 in Unity.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000000005FC818.

This is the stack trace:
image

To me, it seems that RealtimeStreaming throws an exception it could catch later. Often, TCP reads fail when the other party disconnected.

@danilogr
Copy link
Contributor Author

Perhaps add a try-catch here?
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant